bad rom flash, restored, but no activation, no wifi, no data

[horsehockey]

Hope you all can help.

I tried to flash a cm to the zte N9101, but it was rejected by the system, so I rebooted, cleared the system and data, and restored with SupeRr's working rom for this phone.

But since then, I get a solid white line at the boot screen instead of the boot logo (looks like the bmp squished really flat). It then goes to boot animation flashes a bright blue screen in milliseconds, and comes on.

But then even after restoring several times it's still the same, only worse. even restored by backup.ab with adb, it's still the same.

The logo.bmp reappears even after being user deleted. And the EFS folder at root keeps getting deleted.

If I delete the boot animation, I see an animated olive green android lettering logo.

So I have an activation screen with no data or wifi, and iemi = null.

Sorry so long, but trying to explain the details.

 

[SuperR]

Hope you all can help.

I tried to flash a cm to the zte N9101, but it was rejected by the system, so I rebooted, cleared the system and data, and restored with SupeRr's working rom for this phone.

But since then, I get a solid white line at the boot screen instead of the boot logo (looks like the bmp squished really flat). It then goes to boot animation flashes a bright blue screen in milliseconds, and comes on.

But then even after restoring several times it's still the same, only worse. even restored by backup.ab with adb, it's still the same.

The logo.bmp reappears even after being user deleted. And the EFS folder at root keeps getting deleted.

If I delete the boot animation, I see an animated olive green android lettering logo.

So I have an activation screen with no data or wifi, and iemi = null.

Sorry so long, but trying to explain the details.

Never, ever flash a rom that is not intended for your device. My guess is that you overwrote one of your partitions. If you link me to the cm you tried to flash i will take a look and see what partitions you erased. Then, if someone would be willing to grab a backup of theirs, you may be able to restore it/them.

 

[horsehockey]

Thanks.

cm-10-20131006-NIGHTLY-pyramid
CyanogenMod Downloads

Strange things have been happening as well as the activation screen popping up, then even with no data (that I knew of) or wifi, I got a pop-up from us cell saying even with data and gps turned off they can know where we are.

Phone was working at the time I lost connection on reboot..

Edit: When I got that last message last night, I was amazed, as I had no connection to anything accept usb.

But I take it that bad flash did something.

 

[SuperR]

That rom flashed over your data partition (not a big deal probably), and /dev/block/mmcblk0p20 aka tombstones. You should be able to restore this partition from a backup of someone else's Imperial. However, it should be mentioned that there could be personal info stored in that partition. I am not saying there is because I don't know, just tossing it out there.

Here is how someone would backup that partition to help you. You must be rooted to perform the following commands. Open a terminal and type the following, press enter after each line, and wait for it to complete before moving to the next line:

adb shell
su
dd if=/dev/block/mmcblk0p20  of=/sdcard/mmcblk0p20.img

Here is how you would restore it if someone uploads theirs. You must be rooted to perform the following commands. Open a terminal and type the following, press enter after each line, and wait for it to complete before moving to the next line:

adb shell
su
dd if=/sdcard/mmcblk0p20.img  of=/dev/block/mmcblk0p20

Good luck

 

[horsehockey]

Ok thanks SuperR. yeah, i'm fully functional and rooted. just wondering if carrier can reactivate with all the data and all greyed out.

 

[SuperR]

Ok thanks SuperR. yeah, i'm fully functional and rooted. just wondering if carrier can reactivate with all the data and all greyed out.

Nope, you will need to restore that partition before data will work again.

edit: It should be noted that it may not work again even if someone uploads their partition.

 

[horsehockey]

Ok thanks for the info.

... Although I thought thebackup.ab should have backed up everything.

 

[SuperR]

Ok thanks for the info.

... Although I thought thebackup.ab should have backed up everything.

*.ab backups are just apps and app data. No partitions are backed up. This partition is not backed up in cwm either. It is one that should never be touched except by carrier updates. When you flashed the cm10 from the wrong device, the installer used your data partition for /system, and your tombstones partition for /boot. Now tombstones is broken and can probably be restored using the method I posted above. It's your only hope I am sorry to say.

 

[horsehockey]

Thanks. What a lesson to learn.

 

[SuperR]

Thanks. What a lesson to learn.

I hope so lol. Maybe a kind soul will grab that partition for you and you'll be up and running in no time

 

[horsehockey]

That would be nice. :flowers:

I was able to search and download the nv_data.bin and nv_data.bin.md5 as these were somehow deleted.

I've been trying to figure out where they would go, other than the efs file that deletes on reboot. And the logo.bmp keeps returning from somewhere, even though there's only one copy.

 

[DocWebster]

https://drive.google.com/file/d/0B_rIFitEp0rUUDlZNmJLNFhFWjQ/edit?usp=sharing
Visiting northern climes and I see the call of distress. Hope this is the ticket, going back to playing grampa.

 

[horsehockey]

The nv_data.bin files I have, though they are not from this phone itself.

https://drive.google.com/file/d/0B5nqJrEqmYmDLTJGMXR2QnAyYVU/edit?usp=sharing

 

[horsehockey]

I'll give it a try DocWebster. n thanks again (whether it works or not).

 

[horsehockey]

Had to change the sdcard to storage/sdcard1, but still the same.

 

[horsehockey]

Is the EFS folder s'posed to be on the root? 'N do ya know why it keeps getting deleted?

haven't changed permissions. And much thanks to both of you for helping.

 

[SuperR]

I think you should follow the instructions above, flash that partition, then flash a rom for your device. The files you get from other devices could break things so it is not advised.

 

[horsehockey]

You mean after I did the adb dd of DocWebbters, then I should reflash your newest rom?

and should I erase the system and data before flashing.?

sorry. Just tryin' to get it right.

Sorry. just realized the rom formats them anyway.

 

[horsehockey]

Still the same. And mobile network not available. Didn't do the factory reset though.

 

[SuperR]

Still the same. And mobile network not available. Didn't do the factory reset though.

You should certainly wipe data since the rom does not. Also because it was one of the partitions that got messed up. Luckily the data partition can be wiped with no issues.

 

[horsehockey]

Tryin' again.

 

[horsehockey]

Still the same. whatever it is, apparently it's still trying to take control as well, but it strays hidden in there somewhere.

 

[SuperR]

Still the same. whatever it is, apparently it's still trying to take control as well, but it strays hidden in there somewhere.

It was worth a try.

 

[horsehockey]

Yeah. And very much appreciated superR.

You too grandpa (Docwebster)

Sooner or later we'll be able to fix things like this too.

 

[horsehockey]

Still trying to understand why I can actually make a directory of EFS in recovery only to have it deleted by boot.

Still searching for answers. I agree with you SuperR. Something must have gotten deleted from the root partition, and whatever's controlling it won't allow it to be put back on.

Makes me wonder if the carriers can do something like that without our knowledge. Either that or the bad three letter "n" word that deals with "security".