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

Root Messed up, bad.

Downgraded286 said:
Gentlemen.

https://www.sendspace.com/file/k3ccby

The other phone arrived today. I wound up rooting it and installing CWM and making a CWM backup. I backed up to external SD card. I swapped the SD card to my broken phone, did factory reset, wiped cache, and dalvik cache, and system. I restored the recovery. Again I did factory reset, and wiped cache and dalvik cache. I then created another backup. This is that backup. It's a .7z highly doubt the zip itself is flashable in any way...

My phone works flawlessly now.
Click to expand...

I think that the fact a normal cwm backup fixed your phone probably proves my theory about the modem and radio from your phone being the missing piece we need to fix the other JB ROM.

We know it's different bc of the md5 hash, and if you just got a normal cwm backup from the other phone and flashed it on your phone, this would still leave /modem untouched. If that fixed it, then I am very hopeful that I can use the modem.img which you uploaded before to fix the Sprint JB rom from the other thread.

I see from the updater script in the ROM from the ZTE site the syntax for flashing the individual image files and pretty confident that I can replicate this to update our ICS phones with downgraded286's JB image.

Thefatdemon, unless you flash the newer radio firmwares with this ROM you will get the same result as Shinru's nandroid (the boot loops).

I'll work on this tomorrow if I get time before work. This really could come together over the next couple days!

Thanks downgraded!
Cheers,
-SB
 
Cwm is missing your modem.img, but I still have your modem.img from the last nandroid you posted.

Hopefully since the cwm backup fixed your phone without flashing modem.img, then the modem image is probably all I need to fix booting with the 3.4 kernel.

First I will try it with the Sprint JB ROM we've already been working on (bc it already has all the boost apns and such). If that doesn't work I'll start working off of the textnow ROM.

Then I might possibly ask you for some other help, maybe an online nandroid, or possibly if you can from a terminal window or adb shell to use the dd command to create some other image files. dd is easy to use for making image copies of block devices.

I don't think that will be necessary though.

I may not get started on this until after the weekend bc of work.

Cheers and thanks again!
-SB
 
I have something better (I think).

Textnow sent me their stock ROM.

This is how they told me to install it in the email:

OK, I have some instructions and links for you to flash your ROM on your ZTE. Key things to remember here: You will need a micro-USB cable to connect your phone to the computer, and you will need to know your way around the Windows command prompt.

Given that, here's some instructions:

Make sure the ZTE is in DEBUGGING MODE: Settings > Developer Options > USB Debugging (make sure check mark is on)

Download the Android SDK. Get it here:https://developer.android.com/sdk/index.html

We don
 
Sweet, I'll check that out as well.

I'm most interested in the updater script and the modem.img. be nice to see if any other images are flashed.

Cheers,
-SB
 
The textnow rom you linked says it's for the n861. That is not the force, it's the sequent. Be careful flashing it as it may brick your device.

edit: just downloaded it and checked the build.prop...it is not for the force so i highly recommend not flashing it on the force.
 
Downgraded286 said:
Well, that's a shame. What can I do to provide a 100% backup? Nandroid?
Click to expand...

I don't think we need it yet. If you want I'd say use online nandroid backup, but I think we can make a working ROM without it.

We already have your cwm backup, and modem.img from previous nandroid.

I just don't have time to put it together right now.

Cheers,
-SB
 
Hey what gives? I could be wrong but I don't remember seeing Sideload in stock recovery. Didn't that email specifically say to do something you should only be able to do from a custom recovery? I know companies out out their own versions of roms but a non standard recovery is out there.
Also, I now hate and love their customer service. Love that they will give the rom. Hate that it was the wrong one. Boooo!
 
Oh well that would be egg on my face then. I should have known that I wouldn't be right that easily. Still booo for it not being the right version if the Rom. Did you flash that one and get it to work? Or did you just call it good since your device wasn't broken any longer?
 
It would be awesome if you can still try to get the correct ROM from them.

I have an update, I was able to cook your modem image into the sprint JB partial dump we have of the sprint ROM. I still can't get the sprint ROM to boot.

I know the modem flashed bc I can flash any of the 3.0.8 kernel ROMs including DSF and the JB ROM I made but none of the radios work. No wifi, no bluetooth, no cdma.

I tried flashing your cwm backup but still no luck. Won't boot.

Odd thing is your boot image and the one shinru dumped are identical, as evidenced by the md5 check sums being the same.

I haven't had time to flash my backed up modem image yet so can't use my phone. Now my only phone is my Galaxy S4 with freedompop, but since I don't have a sim card I only have service if I have wifi, bc like textnow, freedompop uses data for voice calls.

Cheers,
-SB
 
Do you feel upto some command line work?

I was hoping that you could either open a terminal window or use adb shell, then su to get root.

Next I need some block images converted to image files.

Here are the block devices i would like dumped and the way to copy them. Dunno if you've used dd command before but the syntax is dd if(input_file)=(path) then of(output_file)=(path)

dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/{path to folder you want to save in}/NON-HLOS.bin

dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/{path to folder you want to save in}/boot.img

dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/{path to folder you want to save in}/rpm.mbn

dd if=/dev/block/platform/msm_sdcc.1/by-name/splash of=/{path to folder you want to save in}/splash.img

dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/{path to folder you want to save in}/recovery.img

dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/{path to folder you want to save in}/emmc_appsboot.mbn

dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/{path to folder you want to save in}/tz.mbn

dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/{path to folder you want to save in}/sbl1.mbn

dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl2 of=/{path to folder you want to save in}/sbl2.mbn

dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl3 of=/{path to folder you want to save in}/sbl3.mbn

These are all the image files flashed by the updater-script during the install of the ZTE boost ICS firmware from the ZTE website. I figure if I can get the same images from the JellyBean ROM then we'll be much closer to getting it working.

Also, do you think that you could maybe copy/paste the output from df -h so we can compare the partitions?

I wish I had a phone with this rom so I could do all this myself and not to bother someone else with it. If you can't, don't want to, or don't have time I understand.

Cheers,
-SB
 
Knoobr: I pretty much called it good since my phone is no longer bricked. I might try flashing the ROM just for shits and giggles... I do still have my backup...

sawbones: Sure, I'll give it a shot. If I use ADB will those commands save on my computer or on my phone?
 
About the Dd command... I have heard to be carefull with that because it give no prompts or warnings, so be sure you don't get the paths wrong. But I believe ( abd you should wait to hear what sawbones has to say just in case ) that you can save to comp or sd card depending on what path you specify in the output line. So the "of = " portion would look like" /sdcard"to save to the root of sd but if you out "c:/windows/blahblahblah" then it would save there.
 
Downgraded286 said:
Knoobr: I pretty much called it good since my phone is no longer bricked. I might try flashing the ROM just for shits and giggles... I do still have my backup...

sawbones: Sure, I'll give it a shot. If I use ADB will those commands save on my computer or on my phone?
Click to expand...

I had also opened a support ticket with textnow requesting the rom and I got identical directions and link to rom as you, Downgraded.

I replied and let them know that the rom was for the warp2 (warp sequent), one is snapdragon s2 and the n9100 is s4, also one is single core and the other is dual core. I did request to see if they could provide the n9100 ROM if they are using one.

About ADB and dd, I think knoober is correct but not positive. I would save it to a folder on the sd card just to be certain, then make a tar or zip and share it.


Thanks for your willingness to assist!
Cheers,
-SB
 
knoober said:
Hey what gives? I could be wrong but I don't remember seeing Sideload in stock recovery. Didn't that email specifically say to do something you should only be able to do from a custom recovery? I know companies out out their own versions of roms but a non standard recovery is out there.
Also, I now hate and love their customer service. Love that they will give the rom. Hate that it was the wrong one. Boooo!
Click to expand...

I got the same instructions from them and never mentioned custom recoveries. I haven't played with the bootloader or stock recovery on this phone but it's very possible that one or the other supports adb and/or fastboot, like an HTC.

Still waiting to see what they reply when I informed them that is the incorrect ROM (sequent).

Cheers,
-SB
 
Good news!

I just got a reply from text now support and they gave me links to both an ICS ROM and a JB ROM!

Haven't downloaded yet but am about to. I'll copy and paste the content of the email when I get to my laptop (having trouble doing it with Firefox mobile).

Cheers,
-SB
 
Sasha Antonenko
Nov 06 02:16 PM
Hi there,
Good news! We were able to get the ROM for the N9100 for you. Please check the OS version your device is currently running and use the appropriate ROM:
for the 4.1 version - http://droid.textnow.com/textnow-n9100-jb.zip
for the 4.0 version - http://droid.textnow.com/textnow-n9100-ics.zip

The instructions will be the same as for the Warp we sent earlier.
Thank you,
Sasha

sawbones999
Nov 02 12:56 AM
This is a follow-up to your previous request #65952 "I have a ZTE Force 4g that ..."
Thanks for the reply and willingness to help! Unfortunately this ROM seems to be for the ZTE Warp 2 aka Warp Sequent (zte n861) and not for the Force 4g (zte n9100).
These phones are based on different SOC. One having a snapdragon S2 processor (MSM8655) while the n9100 is based on the snapdragon s4 (MSM8960). I am afraid if I flash this, it might brick my device.
Is this definitely the ROM that you are using on the n9100? If not it would be awesome if it were possible to make the n9100 ROM available!
Thanks so much for your time and assistance!
-Josh
Click to expand...

Downloading NOW!!!!
 
Hmmm....
Doesn't include any radios or firmware images. The boot.img and zImage are a slightly different size than previous versions of the JB boot.img that I have seen. Downgraded's had the same MD5 hash as the one from the sprint ROM.

The updater-script in JB ROM looks like busybox comes installed and symlinked.

I will flash this tomorrow and see if it works on my phone which I have flashed Downgraded's modem image onto and see what happens.

I was just comparing the ICS ROM and the JB ROM that they linked and found something odd for a Carrier ROM, FOTAKILL.apk in /system/app.

Guess they don't want any Sprint updates, LOL.

I may still need those image files...I'll know tomorrow, hopefully.

Cheers,
-SB
 
sawbones999 said:
I may still need those image files...I'll know tomorrow, hopefully.
Click to expand...

This flashable may come in handy for you. I made it for the Warp 4G and modified it slightly for your purposes. It will make a directory, /sdcard/force_partitions, and use dd to create img files in that directory of all the partitions you mentioned :)

force_partition_grabber.zip
 
sawbones999 said:
Hmmm....
Doesn't include any radios or firmware images. The boot.img and zImage are a slightly different size than previous versions of the JB boot.img that I have seen. Downgraded's had the same MD5 hash as the one from the sprint ROM.


I was just comparing the ICS ROM and the JB ROM that they linked and found something odd for a Carrier ROM, FOTAKILL.apk in /system/app.

Guess they don't want any Sprint updates, LOL.

I may still need those image files...I'll know tomorrow, hopefully.

Cheers,
-SB
Click to expand...
My best guess is that this is some esrly vereion if the sawbones mod. Along with the wacky email, im even morr suspicious. Also i tried to pare this puppy down to look like dsf (made the files identical) and the result (to my untrained Eye) exactlybthe same as the sawbones mod. I then went furthur to get and get it booting by following the steps sawbones laid down in the previous 4.1.2 thread but was stopped byb my own dumbness there. I dont know how to unpack a boot img ....yet. long story short, bootloop/restored from backup. Its still fun though
 
knoober said:
My best guess is that this is some esrly vereion if the sawbones mod. Along with the wacky email, im even morr suspicious. Also i tried to pare this puppy down to look like dsf (made the files identical) and the result (to my untrained Eye) exactlybthe same as the sawbones mod. I then went furthur to get and get it booting by following the steps sawbones laid down in the previous 4.1.2 thread but was stopped byb my own dumbness there. I dont know how to unpack a boot img ....yet. long story short, bootloop/restored from backup. Its still fun though
Click to expand...


This truly is the email I got from them. And it definitely is a Textnow branded in rom(I looked around inside the zip and boot.img pretty thoroughly). I just flashed it and same result (Not surprising bc this is based on Sprint's ROM and doesn't include the firmware updates). Disappointing.

I seriously doubt that textnow would use the ROM I posted as a base and then host it on their site, LOL @ knoober :rolleyes:

I guess that's why in the email they said see which version you currently have and flash same, it's bc this isn't really a full update like the ROM for boost on the ZTE site. It's just the original rom, packed for reinstalling.

SuperR's flashable partition grabber looks great! I would be extremely grateful if you could run it, Downgraded286!

Cheers all!
-SB
 
You must log in or register to reply here.
Back
Top Bottom