Stuck in fastboot after downgrade to 2.1 from stock 2.2 - Droid Incredible Q&A, Help & Troubleshooting

I've customized gadgets and electronics before but phones are rather new to me but I'm a very technical person that makes dumb mistakes apparently. Now I seek someone more experienced to put me on the right path.
I'm unable to post links however I followed the directions floating around
directions and now I'm not stuck in the hboot 0.77/fastboot every time it starts. I know my phones not bricked but it's in a very annoying state. I tried a hard reset but this changed nothing.
Currently it's at S-ON and radio 1.00.03 so it seems that downgraded fine. It did get though the whole process fine without error only 2.1 didn't boot up.
I was attempting to do a downgrade so I could root. I had nothing special on the phone so I didn't bother with a backup (besides my sdcard.)
When I run bootloader it tells me "No Images" and "No image or wrong image!" PB31IMG.zip I assume this may have something to do with my problem and I think it's a permissions issue because I didn't re-set them when I backed up my files to format to fat32.
I think this is my problem because I know the files would have lost permissions when I copied. I haven't tried to update again because I assume it will have the same result (that and I've read nasty stories about re-flashing the same version, not that this would do that). I'm unsure on how to get to a shell with the phone in this state or if there is some other way to get it running again. I tried clearing everything and did a hard reset with no luck.
Any help would be much appreciated.
-Blake

Ok I got it working by doing a reinstall. Not sure why it didn't work the first time.

blakeem said:
Ok I got it working by doing a reinstall. Not sure why it didn't work the first time.
Click to expand...
Click to collapse
Reinstall of what? I get the same errors when trying to get any PB31IMG.zip file to load.

dj-anakin said:
Reinstall of what? I get the same errors when trying to get any PB31IMG.zip file to load.
Click to expand...
Click to collapse
I just reinstalled the .zip
What errors?

Ah.
Here's my new thread on my problem.. http://forum.xda-developers.com/showthread.php?t=783123 Been working on it since last night.

Related

Desire Issues

I have been passed a HTC Desire to try and fix after a friend of mine ran into issues trying to put Froyo on it. It was originally with Virgin (Virgin boot screen) but was not locked as other sims were usable.
I've tried various different methods to get it up and running but suspect something he has done with his attempts has caused serious issues - also he is not all that clued up and cannot remember exactly what he did - he did mention that RUU update failed, and also an image he had tried to flash from his sd card had got part way through and then locked up on the radio update.
With the original sim and memory card in, the phone will constantly reboot or just stick at the HTC logo. Take the memory and sim cards out, the phone will boot but system wont launch properly so cant get into settings to enable debugging so I can access the device via ADB. I can get to the fastboot screen, and to the Vol Down-Power screen on start, but if I select recovery it stays on HTC logo and goes nowhere.
I have managed to get HBOOT downgraded to 0.8, but when trying to put on original Virgin RUU it says the main version is older (probably because I'm trying to install an older version over a newer one). The stock Froyo RUU fails and tells me wrong HBOOT and sometimes gives a CID error. Although the phone is not locked, I suspect it will still need a goldcard, but cant create one as I cant get ADB access to the phone.
Sorry if this is a bit of a mess but at work and trying to take calls as well as write this and fix the darned phone. I;m not unfamiliar with methods used to get the phone rooted, but not well up on troubleshooting or working around these issues I have.
Any help would be appreciated.
You should be able to restore it by installing this RUU with a working goldcard:
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
If you get a CID error your goldcard isn't working. There should be no version error with this.
Thanks for the reply....however how can I create a goldcard when I cant get the phone to a point where I can get my pc to recognise it? All the goldcard methods I have seen/tried involve having the usb plugged in and debugging enabled - cant get to that stage as phone wont boot - reboot loop most of the time and when I do occassionally get to the os it doesnt last, it will reboot after a few seconds. Anything else I could do? Or, could I use the card in other phone and create the goldcard in that and transfer over? I do have my own working Desire handset.
Don't know much about this but have read that a goldcard is unique to the SD card not the phone so you could create one on your phone and then use it in your mates. Also, from what I've read it would be worthwhile wiping your mates SD card (make sure he's not added a partition to it), copying a Rom to it, and try to install it using Rom manager (or whatever recovery program which was used to root the phone)
Ok, I used my own phone to sort out the goldcard and currently trying that out now...will keep you posted. Just started the RUU Stock Froyo and seems to have got further so far. Wish me luck!
Mmmmm....ok the RUU worked, but when it restarted (with original goldcard/memory card in, it kept rebooting. It did start once, got to initial setup then promptly rebooted. I swapped out the memory card (no sim in at all by the way at any point up to now) to my own card and after one final reboot it did start up. It doesnt seem stable at all with the original memory card, and still not entirely stable with my card. Could this be a phone fault? Im assuming if the RUU got through all its stages then all areas and files on the phone have been updated correctly and are all correct? Could past failures at updates etc have caused an issue elsewhere?
Have you wiped the various caches? As far as I can make out you need to make sure everything is wiped. I read a post on the OpenDesire thread which suggested that clockworkrom, if that is the recovery program you have installed, may not wipe one of the caches (possibly the dalvik cache) correctly. They recommended another recovery program called something like AmonRu. Although I can't really help you it might be worthwhile saying how the phone was rooted.
Ok, none of this was to root the phone. It was to debrand and put on the HTC Desire Froyo build. Not a custom rom, the standard RUU.
As far as I was aware, an RUU restore of the phone would wipe the appropiate caches, but correct me if I'm wrong. The phone now starts with the standard HTC startup and sound and for all intents and purposes is working, but just cant explain the random reboots. These seem to be worse with the 8GB card that my mate gave me with it. Although, after trying mine and putting the original one back in it seems to have stayed stable up to now. I'm beginning to wonder if there may be an issue with the memory card slot - another swap of the memory card again will probably trigger the reboots once more.
We will see how it goes anyway.
You've got a hardware fault. The RUU will completely reflash the phone, so if it flashed successfully but is still rebooting randomly, it can't be software.
Your probably right. Just started to try and do a downgrade, and after putting the PB99.IMG file on the gold card I made earlier, then starting the downgrade I noticed it stuck at about 98% on the radio update (second item in the list). I'm going to leave it a while to see if I get an error but I suspect it will not move or do anything.
Having gone through this process before on my own handset, I know it doesn't take anywhere near this long. Thing that confuses me though is that the RUU process I went through before went through with no issues - so why would that be able to successfully install a radio update and not this downgrade process? Anyone else had this happen to them?
Update: Ok, leaving this now as I've exhausted all avenues and its obvious the phone is not going to play ball. On another RUU flash it failed (and looking at the logs it was at the radio section and mentioned a partition update failure). A subsequent RUU flash was successful, so at least I've got it back to stock (although it doesnt stay booted long enough to even get the initial setup wizard done now). Passing it back to my friend tomorrow and hope he can get a warranty repair. Just a shame I couldn't get it back to the Virgin firmware. Thanks all those that helped anyway, much appreciated.

Looking for some help...

Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
garaxiel said:
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
Click to expand...
Click to collapse
You're problem is ClockworkMod. Version 5 is a steaming heap of crap that's caused this sort of problem, not only for dInc users, but Tbolt and other device users. The solution seems to be flashing back to an older recovery. And if it works, don't fix. I'm still running version 3.something on my Tbolt and have no plans to change that. I NEVER use ROM Manager and recommend nobody ever touch it except for a few things. I almost never have it installed on any device.
OK then dumb question but if RomManager FC's on me, how do i flash back to a working version or to an alternate version entirely? i have been unable to find other ways of flashing outside of RomManager
Older Recovery versions are available on "dougpiston.com" just follow the directions.
www.dougpiston.com has what you're looking for under "recoveries". They're flashed in hboot like a radio, RUU, splash screen, etc.
Also if that doesn't work, which it probably will, you can also flash a PB31IMG which essentially is the RUU but you do not need a PC. You put that on the root of the SD (as in, not in any folders. Probably know that already...) and reboot into HBOOT (Power and volume down) and itll load it up.
Note: Make sure the file is PB31IMG.zip and not PB31IMG.zip.zip
Ha!!! got it back (well on the road to back anyways)
Was able to find a PB31IMG on dougpiston.com and hboot flashed it in (3.0.0.8). I had one on my PC but it must have been corrupt because it didn't work before. once that was working i was able to get into recovery get a restore back to my 175 nightly and am in the process now of flashing nightly 181 on there cleanly and rebuild the whole phone from scratch. damn i hope this works thanks all for help and ideas.
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
pete_kowalski83 said:
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
No idea...are you using ROM Manager?

[Q] No ROMs taking, keep getting no MD5 message, phone close to bricked.

I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?

Ominous screen after downgrading and installing recovery

I rooted a new aftv last night and all went smooth. Today downgrading and installing cwm very different story.
My aftv now boots to a plain screen displaying the time (incorrectly), a lock symbol and the word "charged" I'm not sure which scared me more. But I'm not bricked. I could still connect with adb and reboot recovery. AND if I hadn't panicked I would've found out sooner that pressing the context menu key on remote takes me right back to the homescreen.
I swear I followed the guides on aftvnews (well done btw!) But every time there was a "if this happens" stipulation in the guides, it happened to me. I can't say it was hard but it was tedious.
Now my issue to I've pushed the correct Rom.zip to my sd card, rebooted recovery but the install fails with this error--Assert failed !less_than_int getprop ro.build.date.utc
I might be missing critical details here to help with diagnosing. Sorry. I've got to work. That process took way longer than expected. I'm hoping it might be enough info to get some ideas. I'll try to check back here later. Thanks.
KLit75 said:
I rooted a new aftv last night and all went smooth. Today downgrading and installing cwm very different story.
My aftv now boots to a plain screen displaying the time (incorrectly), a lock symbol and the word "charged" I'm not sure which scared me more. But I'm not bricked. I could still connect with adb and reboot recovery. AND if I hadn't panicked I would've found out sooner that pressing the context menu key on remote takes me right back to the homescreen.
I swear I followed the guides on aftvnews (well done btw!) But every time there was a "if this happens" stipulation in the guides, it happened to me. I can't say it was hard but it was tedious.
Now my issue to I've pushed the correct Rom.zip to my sd card, rebooted recovery but the install fails with this error--Assert failed !less_than_int getprop ro.build.date.utc
I might be missing critical details here to help with diagnosing. Sorry. I've got to work. That process took way longer than expected. I'm hoping it might be enough info to get some ideas. I'll try to check back here later. Thanks.
Click to expand...
Click to collapse
There's been a few people who have reported the lockscreen oddness. Once you install the update and do a factory reset it will be fine. As for the error, you are not using the correct update. You need to use the prerooted roms.
rbox said:
There's been a few people who have reported the lockscreen oddness. Once you install the update and do a factory reset it will be fine. As for the error, you are not using the correct update. You need to use the prerooted roms.
Click to expand...
Click to collapse
Not being home right now...But following the guide and working from memory...I've got the latest cwm, unlocked boot loader and running 51.1.2.0, my next step would've been to flash
51.1.4.0
If those steps are accurate then from the info I put in the op, I did not install 51.1.4.0 and that's why it failed. I'll bet you're right but I'm pretty sure I pushed the correct version.
It's a bit confusing but doesn't this version require your boot menu. I'm fairly certain the newest cwm does need it. So assuming I pushed the correct version of prerooted fw...would not having boot menu cause the install to fail. Or maybe it's 2 errors on my part but I do remember downloading 51.1.4.0
Thanks a lot! It's in everyone's best interest you don't spend time assisting people like me with something that's probably simple. So if anyone has a comment on my posts please share.
KLit75 said:
Not being home right now...But following the guide and working from memory...I've got the latest cwm, unlocked boot loader and running 51.1.2.0, my next step would've been to flash
51.1.4.0
If those steps are accurate then from the info I put in the op, I did not install 51.1.4.0 and that's why it failed. I'll bet you're right but I'm pretty sure I pushed the correct version.
It's a bit confusing but doesn't this version require your boot menu. I'm fairly certain the newest cwm does need it. So assuming I pushed the correct version of prerooted fw...would not having boot menu cause the install to fail. Or maybe it's 2 errors on my part but I do remember downloading 51.1.4.0
Thanks a lot! It's in everyone's best interest you don't spend time assisting people like me with something that's probably simple. So if anyone has a comment on my posts please share.
Click to expand...
Click to collapse
The only way to get the ro.build.date.utc failure is by using a stock package. My prerooted roms simply do not have that check in them. It fails on that line precisely to prevent people from installing stock packages.
rbox said:
The only way to get the ro.build.date.utc failure is by using a stock package. My prerooted roms simply do not have that check in them. It fails on that line precisely to prevent people from installing stock packages.
Click to expand...
Click to collapse
Thanks a lot! You probably saved me a lot of time trying to figure out where I went wrong. When I get home I'll delete the Rom I pushed, push the correct one, if it installs right I think my next move is your boot menu. But I'll double or triple check that later on tonight.
Edit--install 51.1.4.0 updated version then, if I follow correctly, I can install the latest prerooted fw.
I did everything I said I was going to do and it went smoothly. I'm now running prerooted 51.1.40
There's just one thing. I was certain I unlocked bootloader earlier today. From what I know it's not possible to have the latest cwm with a locked bootloader. But when I clicked unlock bootloader in adbfire (the program I use for my other aftv) it says "bootloader not unlocked"
So I was second guessing myself. But couldn't explain how I missed it and still had the latest cwm. I checked and aftv-unlock was there in my adb folder. I wouldnt have put it there if I didn't transfer it. But to be on the safe side I went back into the terminal and unlocked my bootloader (I believe for the 2nd time). THEN i hit the unlock bootloader on adbfire again and it still returns with "bootloader not unlocked"???
Is it because busybox was not installed through adbfire? If I use it on my other aftv it says "bootloader unlocked" so the software definetly can confirm it. It's just not...
Normally I'd go ahead and install rbox's boot menu then the latest firmware, but many more things have gone wrong in the last 24 hours (not tragically wrong) but just enough for me to wait for an answer on this and maybe stop for the night. Everything's working great (knock-wood) but I assume when rbox finishes android tv I'll need the boot menu. So I'll wait here patiently for both. Thanks.

[Q] Kernel Panic Upload mode

My SM-T210 (Galaxy Tab 3 7.0 Wifi) XSP region which was running fine for over a year starting giving me the Kernel Panic Upload Mode errors in the last few days.
It is absolutely stock - still running Android 4.1.2, never rooted, etc.
From previous threads on this error, it seems that doing a factory reset in recovery ought to fix this. However, I can't quite seem to do the factory reset. Doing it from Android settings just seems to go into recovery. And from recovery, after telling it to do the data wipe/reset and rebooting, I'm back into Android with all of my apps and settings still in place.
So I'm a newbie and don't know what to do from here. Any suggestions please?
Ok, I've tried to flash the TWRP recovery by following the instructions at http://forum.xda-developers.com/showthread.php?t=2437219. But even after getting "RES OK", I did the reboot into recovery, and went straight back into the stock recovery. wtf... it seems as though writes to the internal storage are accepted but ignored.
Still hoping for some pointers, please...
I'm guessing that the problem is that the writes appear to succeed but actually did not take place at all. To test this, I've booted up, used ES File Explorer to create a "test" file and rebooted. Upon rebooting, the file has disappeared even though the kernel did not panic during this process.
Has anyone seen such symptoms before? My search-fu is lacking, and I can't find appropriate search results.
webbrowser said:
Still hoping for some pointers, please...
I'm guessing that the problem is that the writes appear to succeed but actually did not take place at all. To test this, I've booted up, used ES File Explorer to create a "test" file and rebooted. Upon rebooting, the file has disappeared even though the kernel did not panic during this process.
Has anyone seen such symptoms before? My search-fu is lacking, and I can't find appropriate search results.
Click to expand...
Click to collapse
I have heard many stories before about kernel panic upload mode. I believe it might be a kernel issue in which changing it would be a good idea or some sort. That's all I know ?
-DUHA
DUHAsianSKILLZ said:
I have heard many stories before about kernel panic upload mode. I believe it might be a kernel issue in which changing it would be a good idea or some sort. That's all I know
-DUHA
Click to expand...
Click to collapse
Roger. I've tried to flash the TWRP recovery via ODIN, but the writes did not seem to work despite "RES OK". Flashing recovering is required before I can change the kernel right?
For what it's worth, my symptoms seem to match the "emmc brickbug".
I've found what appears to be instructions on how to fix this after the brickbug has occured here (these are for different devices, but I suppose it oughta work):
http://forum.xda-developers.com/showthread.php?t=1823918
http://forum.xda-developers.com/showthread.php?t=1667886
Unfortunately, I can't seem to run the zips from my stock recovery, as signature verification fails. And I don't think I can install a custom recovery at this point now, since all writes seem to fail. So I'm still stumped, and I think I have a brick :crying:

Categories

Resources