• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root So dont laugh but my force is broken...

knoober

knoober

Android Enthusiast
...and this how it happened in recipie form.
Gather ingredients:
1 boost mobile ZTE force
1 owner who wants the best but is far to eager to play with stuff
1 script " dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13" in a terminal emulator
Mix together with one download of a recovery img you have been assured will work for your phone. Reboot and enjoy one freshly bricked ZTE force.

That's how I broke it. Since then I have learned how to install CWM with adb and have successfully fixed 2 other phones. So my understanding of what I should have done is there. Like I said don't laugh I'm only breaking my own stuff so far :)
Here's the biggest issue though, I be got no FTM and no recovery available. Adb device command shows a list if devices response but no serial number . So now the big question.... Am I sporting a parts phone? Thanks in advance.
 
Hey knoober,

I'm guessing /dev/block/mmcblk0p13 is not the recovery partition for your device?

I've moved your thread over here to the all-things-root area for you.

Hopefully the good folks in here can help you out :crossing-fingers: :thumbup:.

Cheers and best of luck!
 
Not the recovery partition fir my device ... That is highly reasonable. I was trying to instal CWM recovery manually, and I never thought there might be different partitions on different phones. I mean I knew some stuff was specific to your model but I figured there was s certain generic stock that all devices would start with.Have you got any resources about partitions you would recommend?
Now having learned that it sounds like I flashed something over the boot img and now I need to replace that. Without access to ftm or recovery. I think I may have an awesome new ppr weight.
 
If you cant access ftm or recovery I think you now have a paper weight.
This was the command you were supposed to do
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Click to expand...
 
Well it would still be a cool ppr weight.... Script is still above my head. So is most of this root stuff but I am wondering if I can't wipe the whole machine and start from scratch... Like installing an OS ON a comp...format then install? I guess I'm hopefull because even though adb devices doesn't show anything it still shows a blank list instead of saying it can't find the device.
 
Try and boot into fast boot by pulling the battery and Holding Power + Volume Up button and then put the battery back in.
Once there pull up adb and check devices.
 
Forgive me since I don't own the ZTE Force 4G LTE device, but booting into fastboot or bootloader mode would not normally allow adb to see/recognize the device [i.e., via adb devices] (the adb daemon typically only works when a custom recovery is running or when normal Android is running and USB debugging has been enabled).

If you've got the (fastboot) proper drivers setup for your device and you boot into fastboot/bootloader mode, you should be able to use the fastboot devices command to see if you have fastboot connectivity.

If your bootloader is unlocked, then you might be able to reflash or softboot a new recovery or Android boot image--but you'd have to rely on the others in this all-things-root area to discuss/inform about the unlock status of your bootloader (I have no idea whether it is or not).

Best of luck!
 
Fastboot tries to connect, says "waiting for device" but never does anything ( I left it sit all night once) none of the commands produce any result except the waiting message. That's why I'm hoping to start from scratch... Maybe put Windows on it or something :) but I can't find a way to wipe the device at that level. I have a working recovery and a Rom that boots ( I actually own 2 of this model and can verify that these files work ... Thanks SuperR) I just need a way to start from scratch... Like ALL THE WAYfrom scratch. Thanks again
 
Hehe, That was my fault, I gave you misleading information about the adb part, Scary Alien is right, You would need to pull up fast boot and try and flash your recovery that way.
And just an fyi, This phone comes with the bootloader unlocked by default. I'm not to sure but I think all ZTE phones come unlocked.
 
I've read that the boitloader for this one is simply a black screen so other than the devices command (am I wrong ? Is it fastboot devices? Or adb devices?) I have no way to know where I've gotten with the bootloader. First, like I said there is no ftm or recovery, when I power on I get a black screen and a solid red light on the led. Then any adb or fastboot command returns a "waiting for device" message. My theory is that the bootloader is damaged but partially loaded.
 
The Bootloader is simply a black screen, for FastBoot to read it you need to boot while holding the up volume button, like recovery, just a different button.
 
up+power is ftm... not fastboot i dont think, only the zte online updater can connect to ftm, to get to bootloader i thought the only way is to use adb to reboot bootloader. i could be wrong though

as far as im aware your only hope is some sort of adb connection, if you cant get into adb youre just done for because you did indeed overwrite the wrong partition and theres no way to go back from a mistake like that
 
What if I use the same command that I broke it with but flashed the right file? How do I find out what is supposed to be there when things r working? No way to blank the whole device and start from scratch?
 
Went back today because I thought maybe I could try some other commands I read about and then realized I had been reading things wrong "adb devices" always threw a blank list ( which I found encouraging because it wasn't an error ). Tried "fastboot devices" and got the error message. I beleive you guys now ... My poor little.phone is only good for parts now. Lucky I have another working Force huh? Anyways I hope I didn't waste anyone's time , I just hate to give up on a device. Thanks again.
 
You must log in or register to reply here.
Back
Top Bottom