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

Root bricked zte

hello im new to this whole rooting thing...anyways I rooted my zte warp sequent using doomlord,after I deleted a few system apps,but none of the actual os apps,then rebooted and now its in a stuck constant reboot mode. the phone comes to zte logo,and that's it. I can bring my phone into system e3 recovery or the ftm mode. also I used rom manager and flashed clockwork mod recovery. I reformatted my sd card on my computer using the thourough method,different formats fo the card on pc are ntfs,fat32,exfat32....so I don't know what to do.....can anyone please help?
 
thanks lilbit. but yea umm you might be in a pretty bad situation. rom manager seems to have an issue working right on the sequent so it wont actually put a custom recovery on your phone. you have the stock recovery, which is effectively useless, and ftm mode which might help if you havent updated to version b09. try the online update tool from zte's website see if that works out for you, if not you may be stuck unless you can manage to get an adb connection into the phone while in that bootloop in which case i should be able to help

you have to be careful of things like this, the programs can be linked together in such a way that even the removal of the most insignificant application could cause a domino effect causing the entire os to come to a hault

get my AIO tool, boot the phone up and let it sit in its frozen state for a few minutes, just let the zte logo sit there, then with it plugged into the computer you used to root it run the driver checking function of my aio tool to see if it has a connection to the device. if it does you can then use the tool to install cwm, i would personally recommend the fastboot method but the terminal method may work
 
Yeah pretty much what junkie said lol. Hey junkie any reason why ROM manager doesnt flash the recovery on the sequent? or is it the stock init.d script that automatically install stock recovery on boot if it was replaced with cwm?
 
shouldnt be a script to replace the recovery on boot. i think it has something to do with it not getting proper root permissions, i never had any popup saying it asked for root to be able to actually do the things it was supposed to do, or maybe the method its trying to use just isnt compatable. i dont really understand how rom manager does what it does fully so im no expert on the subject but i know it just plain doesnt work most of the time
 
Yeah it could be rom manager if it didn't even ask for root permissions.

The file in /system named recovery-from-boot.p and the file in /system/etc named install-recovery.sh they comes stock on almost all Stock roms since mid last year and if you had a phone runing 2.3.6 before mid last year if you ever had an OTA for any reason theres a good chance theses files we're also installed but from here up almost all Stock roms have theses files.
Runs at boot to make sure cwm is uninstalled from your device when you install it. have you ever gotten a prompt while exiting cwm that says would you like to disable blhahahaah whatever the hell it says lol, its talking about thoses files. if you wanna disable them. this is how it does it on the sequent
it already knows the stock recovery md5sum code so when it checks the current recovery installed md5sum if it doesnt match up with the on in the script it automatically replaces it.
PHP:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p13:2048:0de407d956129cb458b59728dc560883f573de14; then
  log -t recovery "Installing new recovery image"
  applypatch EMMC:/dev/block/mmcblk0p12:4657152:2e02431ab6bf21085675c0c8af8ebef8dfb9139d EMMC:/dev/block/mmcblk0p13 d51dc1ca31a5fccd9467b46a4e7d94026e489fc5 6668288 2e02431ab6bf21085675c0c8af8ebef8dfb9139d:/system/recovery-from-boot.p
else
  log -t recovery "Recovery image already installed"
fi




EDIT

I think your AIO tool removes it while it installs cwm but since he did it from rom manager i dont think it removes it.
 
those files arent present and it doesnt have any prompt in cwm to disable it. plus i dont see how my tool would remove it, all i did was either force it to manually overwrite block 13 with the terminal method or reboot into fastboot and do a simple "fastboot flash recovery recovery.img" other companies may do it but this phone never had that feature from what i have seen

and if youd like to see exactly what my aio tool does theyre just batch files that you can open with any text editor. fastboot.bat and terminal.bat. extremely simple straightforward programs

i wrote the recovery flashing parts by hand, the only thing i didnt write is the root scripts, those were doomlords
 
huh, interesting. i never had a copy of b09 with it in there but my copy wasnt obtained through the ota, it was the early crapped up version from the update tool
 
yeah it might of only came with the ota cause i think i remember seeing the file with es file explorer when i updated my phone out of the box when after i got it. its like a little init.d script, i first saw it when an update came in on my Samsung Transform ultra last year for bug fixes.
 
yea i never updated my samsung either lol. i had cwm, didnt feel like screwing around trying to get the update, so i just left it factory. mind you that ota popup bugged the hell out of me for the longest time. that was before i learned anything about android really though so i didnt know how to disable it lol

like i said though my copy didnt have those files i dont think and rom manager still didnt work, and there is nothing in my cwm scripts that would disable it, so i have not a clue
 
One word "ROM TOOL BOX PRO" lol .. It puts the updated version of CWM touch on the device.... or use junkies tool. Best ways to put custom recovery.
 
One word "ROM TOOL BOX PRO" lol .. It puts the updated version of CWM touch on the device.... or use junkies tool. Best ways to put custom recovery.

Umm... How? I've Had the ROM Toolbox Pro for a while now... Just don't really know how to use it...
 
My work WiFi was down all day, You go to the first page on ROM tool box pro, not ROOT tool box pro, i use to get the two confused, but its in the recovery sub menu, i believe it says flash recovery, Clockwork mod apk is not good at all, it freezes or gives you an error. flash 6.0.27 touch and your done, but i have to say Junkies AIO tool works really well, try it out. I was experimenting, going from root to unroot and back to root and i did it with Junkies tool.
 
Right on. I've had CWM touch for a while but didn't know u could use the toolbox. Thanx bro :smokingsomb:
 
Yeah pretty much what junkie said lol. Hey junkie any reason why ROM manager doesnt flash the recovery on the sequent? or is it the stock init.d script that automatically install stock recovery on boot if it was replaced with cwm?

I actually managed to install CWM using ROM manager, but I may have screwed up. It said something about deleting something because it could delete CWM on boot, and I did it. My phone works fine and I can get into CWM, though, so I don't think I screwed up too bad.
 
Back
Top Bottom