Hello there.
My Prime recently went out of warranty and I decided to root and install a custom rom.
I was and still am a newbie when it comes to flashing roms but i stayed true to the guides and followed every step.
I managed to back it with nvflash so everything is safe from that point of view.
After the androidroot recovery, i switched to twrp 2.6.0(a mistake in my opinion now that i have learned certain thing) and followed the steps to installing the androwook rom 2.31.
I flashed the hairybean bootloader and recovery updater - nothing happened to the twrp version as it should have and i noticed nothing happened to bootloader version (it still was 10.4.2.15). I continued with the guide and managed a successful install of the rom with husbunduah kernel.
That's when the problems began with the constant reboots(at about 1min-1,5 min). I reinstalled the rom with other kernels and it only became worse.
I thought it was because of the bootloader - but after all the wipes and reflashing of the updater - it still wouldn't change.
I downgraded the twrp to 2.3.1 and tried it again, thinking i would see the upgrade on the version of twrp and it would work with the bootloader.
All the images were checked with md5checker and i did all the wipes in the order it was written and when i should've done them.
Please lend me a little hand here as i am unsure if i'm correct in my assumptions and don't know what to do next.
to summarize: the question is - how do i update the bootloader and why didn't it upgrade?
cherokee990 said:
Hello there.
My Prime recently went out of warranty and I decided to root and install a custom rom.
I was and still am a newbie when it comes to flashing roms but i stayed true to the guides and followed every step.
I managed to back it with nvflash so everything is safe from that point of view.
After the androidroot recovery, i switched to twrp 2.6.0(a mistake in my opinion now that i have learned certain thing) and followed the steps to installing the androwook rom 2.31.
I flashed the hairybean bootloader and recovery updater - nothing happened to the twrp version as it should have and i noticed nothing happened to bootloader version (it still was 10.4.2.15). I continued with the guide and managed a successful install of the rom with husbunduah kernel.
That's when the problems began with the constant reboots(at about 1min-1,5 min). I reinstalled the rom with other kernels and it only became worse.
I thought it was because of the bootloader - but after all the wipes and reflashing of the updater - it still wouldn't change.
I downgraded the twrp to 2.3.1 and tried it again, thinking i would see the upgrade on the version of twrp and it would work with the bootloader.
All the images were checked with md5checker and i did all the wipes in the order it was written and when i should've done them.
Please lend me a little hand here as i am unsure if i'm correct in my assumptions and don't know what to do next.
to summarize: the question is - how do i update the bootloader and why didn't it upgrade?
Click to expand...
Click to collapse
Cherokee.. I am pretty busy at the moment working on Android TV boxes but I can see that you have nflash backups so everything should be fine.
I will pm you my Google talk address and add me on there with a message saying who you are, this is a bit too complicated to go through on the forums.
Can't promise you I can help you straight away but I will get around to it in the next day or two.. I'm UK time by the way.
Related
Hi, This topic should have been a reply to the AiO one on the development board but since the board software thinks I'm too new to post to developments forums I'm forced to create a new topic here on General, So I'm really sorry if I did something wrong (Guess what, I'm new!)
So, I wanted to upgrade my Tablet S to a pre-rooted ICS while I had a 3.2.1r2.
I rooted it, did all the steps to have a working custom_update.zip,while flashing the custom_update thing, text warned me that I was flashing the pre-rooted, init.d'ed, whatever custom rom, so I though it was all going to be fine..
Then I discovered that Superuser wasn't there, neither was busybox and basically root in general was gone, while the "rescure-backdoor" wasn't.
Checking the topics I discovered that my best solution was to downgrade to 3.2.1r2 and do the whole thing again.
So that's what I did, I wiped the whole system and Honeycomb started without problem, except that it turns back to not-really-pre-rooted ICS the next time I reboot.
This wouldn't be a problem if it wasn't for the fact that I need to reboot the tablet some times to get root, and I need root to decrypt and prepare the custom update.
So, what am I doing wrong? I searched here and there and didn't find a solution yet .
Sometimes you need to do a factory reset or else it flips back to ICS from HC. I haven't always had to do it; I'm not sure what the contributing factor is there. Essentially there are two system partitions (system0 and system1) and the bootloader makes a decision on which one to boot based on unknown criteria. It can be a bit quirky after downgrading, but a factory reset seems to clear it up.
SOLVED.. but how?
I knew that, I wiped everything each time I reverted to 3.2.1, maybe I forgot to mention that.
But it didn't directly boot to ICS, it did boot to Honeycomb, THEN the next time I boot I'm back to ICS again.
I did manage to stop this, however.. how? I don't know, something like the 4/5th time I re-flashed it worked.
Hamcha said:
I knew that, I wiped everything each time I reverted to 3.2.1, maybe I forgot to mention that.
But it didn't directly boot to ICS, it did boot to Honeycomb, THEN the next time I boot I'm back to ICS again.
I did manage to stop this, however.. how? I don't know, something like the 4/5th time I re-flashed it worked.
Click to expand...
Click to collapse
Wipe before first boot of 3.2.1 is VERY IMPORTANT.
Downgrade step-by-step is described in AiO thread in FAQ section.
br
condi
Hi all,
Some background information, I was using team eos nightlies and I wanted to change the rom to see whether if others are any better, so i did cleared the cache/delvik cache and as well as did a factory wipe. Then i installed the the that I wanted to try out, the Energy rom, however, after flashing, I couldn't get past the asus spalsh screen, I can still go back to the twrp recovery though.
I tried flashing back my original team eos nightly.. and it booted without any problem.
Anyone knows if i'm missing any step to flashing a new rom?
ZeitiaX said:
Hi all,
Some background information, I was using team eos nightlies and I wanted to change the rom to see whether if others are any better, so i did cleared the cache/delvik cache and as well as did a factory wipe. Then i installed the the that I wanted to try out, the Energy rom, however, after flashing, I couldn't get past the asus spalsh screen, I can still go back to the twrp recovery though.
I tried flashing back my original team eos nightly.. and it booted without any problem.
Anyone knows if i'm missing any step to flashing a new rom?
Click to expand...
Click to collapse
Sounds to me like your on the older ICS bootloader and the other roms you've tried are using the JB bootloader (lucky you havnt bricked your device)
You need to upgrade the Bootloader first in order to install these roms but BEWARE, once you upgrade the bootloader, you cannot go back to the ICS bootloader or roms.
Unless you have backed up NVFlash and you restore your device/bootloader with NVFlash.
Now would be a good time to do your NVFlash backup if you havnt already, then go from there.
Click the link for a guide on upgrading the bootloader by Flumpster in the Androwook thread ... there is also a link for the NVFlash guide
http://forum.xda-developers.com/showpost.php?p=34938455&postcount=6212
Danny-B- said:
Sounds to me like your on the older ICS bootloader and the other roms you've tried are using the JB bootloader (lucky you havnt bricked your device)
You need to upgrade the Bootloader first in order to install these roms but BEWARE, once you upgrade the bootloader, you cannot go back to the ICS bootloader or roms.
Unless you have backed up NVFlash and you restore your device/bootloader with NVFlash.
Now would be a good time to do your NVFlash backup if you havnt already, then go from there.
Click the link for a guide on upgrading the bootloader by Flumpster in the Androwook thread ... there is also a link for the NVFlash guide
http://forum.xda-developers.com/showpost.php?p=34938455&postcount=6212
Click to expand...
Click to collapse
Ohhh is it. I don't remember anything about the bootloader so I just assumed that since I was on TeamEos JB nightlies, then I'm on JB bl.
I went to flash many other roms to tried too. Must've been really lucky then.
Thanks for the help, I'll go try it out.
I have a 4.1.1 Transformer Prime that I was finally able to unlock last night. After unlocking I followed this blog post to get nvflash setup and download all of my backups. Up to this point everything went smoothly.
After such I loaded CM 10.2 and Google apps on a flash drive to load the rom but even after many reboots Flatline would not see my microSD card. It would still boot to the stock rom at this point so I booted up and put the rom and apps on the internal storage and got back into Flatline. At which point I kept getting errors for mounting the internal storage. I loaded TWRP recovery hoping for different results but found that it asked for a password right away when going into TWRP. This helped me figure out that for some reason my internal storage was encrypted. After reformatting the internal storage I was able to load TWRP without it asking for a password. Since TWRP was already loaded I tried using it to isntall CM 10.2 and gapps. Install went clean but it would never boot the rom, just bootloop. At this point I had trouble getting back into recovery, it would just bootloop and ignore my Vol down press. Eventually using nvflash as an exit to the boot loop I was able to get back into recovery. I then tried to flash CM10.1 with similar results, no bootloop, just hang at the Asus screen.
At this point I decided to change gears a little and thought I would try Androwook after seeing all the posts about it. So I loaded up the files onto my microSD and and double read the post and loaded the Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip. After the blue bar filled and it rebooted I was presented with a signature failure error, bootloader 0x000..8. Very discouraging. Booted into nvflash again, but I was presented with a problem, which is very similar to the state I am currently in.
My bootloader is hosed, I cannot get to recovery, and I am unsure as to how/which file to use for recovery from the backups I made earlier. After some searching I found a post with the ICS bootloader linked. I downloaded it and loaded it through nvflash and now I am back to having access to fastboot and recovery again. However, the bootloader version is an old version, AndroidRoot 9.4.2.28. I searched some more and found a post that claimed the bootloader was AndroidRoot 10.4.2.15. I snagged it, loaded it up through nvflash but it wont let me into recovery or fastboot. I loaded a JB recovery through nvflash hoping it might help, but it didnt. So now I'm trying to get back to something I can use. Even a stock Prime is better than one that cannot boot roms. I tried loading Flatline recovery hoping to use it to load the JB bootloader again, but it doesnt seem to ever load in the ICS bootloader.
So currently I have nvflash working, the AndroidRoot 9.4.2.28 bootloader, with TWRP ICS 2.6.3.0 as the recovery. I am hoping someone can help me get this thing to a point where I can load a rom that works or back to a stock rom.
xFoCaLx said:
I have a 4.1.1 Transformer Prime that I was finally able to unlock last night. After unlocking I followed this blog post to get nvflash setup and download all of my backups. Up to this point everything went smoothly.
After such I loaded CM 10.2 and Google apps on a flash drive to load the rom but even after many reboots Flatline would not see my microSD card. It would still boot to the stock rom at this point so I booted up and put the rom and apps on the internal storage and got back into Flatline. At which point I kept getting errors for mounting the internal storage. I loaded TWRP recovery hoping for different results but found that it asked for a password right away when going into TWRP. This helped me figure out that for some reason my internal storage was encrypted. After reformatting the internal storage I was able to load TWRP without it asking for a password. Since TWRP was already loaded I tried using it to isntall CM 10.2 and gapps. Install went clean but it would never boot the rom, just bootloop. At this point I had trouble getting back into recovery, it would just bootloop and ignore my Vol down press. Eventually using nvflash as an exit to the boot loop I was able to get back into recovery. I then tried to flash CM10.1 with similar results, no bootloop, just hang at the Asus screen.
At this point I decided to change gears a little and thought I would try Androwook after seeing all the posts about it. So I loaded up the files onto my microSD and and double read the post and loaded the Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip. After the blue bar filled and it rebooted I was presented with a signature failure error, bootloader 0x000..8. Very discouraging. Booted into nvflash again, but I was presented with a problem, which is very similar to the state I am currently in.
My bootloader is hosed, I cannot get to recovery, and I am unsure as to how/which file to use for recovery from the backups I made earlier. After some searching I found a post with the ICS bootloader linked. I downloaded it and loaded it through nvflash and now I am back to having access to fastboot and recovery again. However, the bootloader version is an old version, AndroidRoot 9.4.2.28. I searched some more and found a post that claimed the bootloader was AndroidRoot 10.4.2.15. I snagged it, loaded it up through nvflash but it wont let me into recovery or fastboot. I loaded a JB recovery through nvflash hoping it might help, but it didnt. So now I'm trying to get back to something I can use. Even a stock Prime is better than one that cannot boot roms. I tried loading Flatline recovery hoping to use it to load the JB bootloader again, but it doesnt seem to ever load in the ICS bootloader.
So currently I have nvflash working, the AndroidRoot 9.4.2.28 bootloader, with TWRP ICS 2.6.3.0 as the recovery. I am hoping someone can help me get this thing to a point where I can load a rom that works or back to a stock rom.
Click to expand...
Click to collapse
Fair play, at least you tried and you probably learnt a lot in the process.
You have nvflash backups so don't panic. It is fixable.
I am going to send you my google talk address now over PM. Add me by going to gmail on your PC in your browser and adding me in the bottom left hand corner to chat. I will try and talk you thru it.
If you finally get to boot your transformer prime, would you mind posting here what caused all that mess and the steps you followed to solve it?
PD: Flumpster, I've been reading this forum for a week since tomorrow arrives my transformer prime, which i recently purchased on another forum, and I hope to unlock it, then run nvflash to backup the whole thing and finally install hairybean without any trouble. I would like to thank you for all the work you have done this far helping people to solve their bricks. I really appreciate the way you explain everything, it helps me understanding all this stuff. Great Job
puntxo said:
If you finally get to boot your transformer prime, would you mind posting here what caused all that mess and the steps you followed to solve it?
PD: Flumpster, I've been reading this forum for a week since tomorrow arrives my transformer prime, which i recently purchased on another forum, and I hope to unlock it, then run nvflash to backup the whole thing and finally install hairybean without any trouble. I would like to thank you for all the work you have done this far helping people to solve their bricks. I really appreciate the way you explain everything, it helps me understanding all this stuff. Great Job
Click to expand...
Click to collapse
This was a new one on me and I have no idea how he got himself into it but we managed to fix it anyhow.
He was the first person I have helped tho that needed to restore unlock-token.img, factory-config.img and bricksafe.img as he had some error saying failed to inject certificate, unrecoverable bootloader.
As long as you have all your nvflash backups you will be fine amigo.
As the title says, I'd like to flash Ditto Note 3 ROM v5.2. I am currently running Alliance ROM build 26 with TWRP 2.7.2.0.
What I'm looking for is a basic step-by-step (I feel pretty confident about finding detailed breakdowns of each step so please don't put yourself out too much--I'll follow up if there's anything I don't understand) so that there's nothing I miss, leaving me with a bricked phone, a locked bootloader that I can't revert, or non-functional radio/modem/anything.
I'm fine with ODIN, flashing, recovery, and other basics. I'm really just looking for each step that is ABSOLUTELY REQUIRED in order to not run into the problems mentioned above. I'd like to be able to get back to where I'm at now in case I decide I don't care for DN3. Thank you in advance.
I've attached a screenshot of "About Phone" in case the info helps.
I've also never taken an OTA or used an OFFICIAL stock ROM except for the one it came with, I rooted and unlocked as soon as it was possible after day one of release with no updates/upgrades prior (pre-ordered from Verizon, first ROM was BeansTown build 1 ).
Is what I'm asking possible? Can this be done without relocking the bootloader?
Applejackson said:
As the title says, I'd like to flash Ditto Note 3 ROM v5.2. I am currently running Alliance ROM build 26 with TWRP 2.7.2.0.
What I'm looking for is a basic step-by-step (I feel pretty confident about finding detailed breakdowns of each step so please don't put yourself out too much--I'll follow up if there's anything I don't understand) so that there's nothing I miss, leaving me with a bricked phone, a locked bootloader that I can't revert, or non-functional radio/modem/anything.
I'm fine with ODIN, flashing, recovery, and other basics. I'm really just looking for each step that is ABSOLUTELY REQUIRED in order to not run into the problems mentioned above. I'd like to be able to get back to where I'm at now in case I decide I don't care for DN3. Thank you in advance.
I've attached a screenshot of "About Phone" in case the info helps.
I've also never taken an OTA or used an OFFICIAL stock ROM except for the one it came with, I rooted and unlocked as soon as it was possible after day one of release with no updates/upgrades prior (pre-ordered from Verizon, first ROM was BeansTown build 1 ).
Is what I'm asking possible? Can this be done without relocking the bootloader?
Click to expand...
Click to collapse
Since you are already using Alliance B26 (an MJ9 based ROM), you shouldn't need to use ODIN for anything.
I simply followed the instructions in the DN3 post, and I was up and running w/o issues.
I'm not sure about TWRP, bc I used the latest version of Philz myself, and had no issues. I've heard of some people not having issues with TWRP, and others who did. Seems like YMMV, based on all the posts I've gone through in that thread (you should go through it yourself and get an idea).
Also, I am having the odd lockup every so often with this ROM (I believe it is deep sleep based), which a few others are also experiencing. Outside of that, I love the ROM too.
Thanks for the reply.
devious_z said:
Since you are already using Alliance B26 (an MJ9 based ROM), you shouldn't need to use ODIN for anything.
I simply followed the instructions in the DN3 post, and I was up and running w/o issues.
I'm not sure about TWRP, bc I used the latest version of Philz myself, and had no issues. I've heard of some people not having issues with TWRP, and others who did. Seems like YMMV, based on all the posts I've gone through in that thread (you should go through it yourself and get an idea).
Also, I am having the odd lockup every so often with this ROM (I believe it is deep sleep based), which a few others are also experiencing. Outside of that, I love the ROM too.
Click to expand...
Click to collapse
Thanks for taking the time. I guess my main concern was with the bootloader and whether or not I had to upgrade it and possibly lock it accidentally, or if I could just stay with the bootloader I have now, which is actually VRUEMJB. Used the method outlined in the AllianceRom thread for flashing the ROM. Since I still have a virgin bootloader I didn't want to lock it. I think I'll just try flashing the ROM as I have it, after a wipe of course, and I can always flash a recovery backup if need be.
I did try looking through the info in the threads for the ROM, but there are thousands of pages on the original and 90+ in the [**UPDATED] Verizon DN3 thread. The ones that I have read through have some conflicting information, so this query is really just to eliminate any confusion on my part before changing anything I can't change back.
Update: Tried and failed.
Just an update, I tried with my current configuration as I said I would above. Factory Reset, Data Format, the whole nine yards, and everything seems to go smoothly until the final reboot after everything is installed. The phone just hangs on the Samsung boot image and never goes any further. Tried reinstalling twice after but always the same problem. I was able to flash my previous backup no problem, so no damage, but no joy either. Any ideas?
Applejackson said:
Just an update, I tried with my current configuration as I said I would above. Factory Reset, Data Format, the whole nine yards, and everything seems to go smoothly until the final reboot after everything is installed. The phone just hangs on the Samsung boot image and never goes any further. Tried reinstalling twice after but always the same problem. I was able to flash my previous backup no problem, so no damage, but no joy either. Any ideas?
Click to expand...
Click to collapse
I guess I would start with reinstalling the MJ9 firmware through odin, and then try the rom again. You mentioned you were actually on MJB earlier which doesn't sound right.
Hi everyone,
I would like to preface with I made some very stupid mistakes late last night/early this morning. I decided at around 11pm I was going to root and install a custom recovery on my SGP311. I followed this guide exactly to obtain root and recovery and it worked PERFECTLY.
http://forum.xda-developers.com/xperia-tablet-z/development/root-sp321-ftf-10-5-1-0-283-t2873377
Then the mistakes started happening. First mistake I made.
1) Instead of backing up everything in recovery I just Wiped everything. I deleted cache, davlik cache, system, and data. I thought at the time no big deal ill just flash a rom.
2)I decided to flash a CM nightly and I got the "your device is a pollux and this rom is for pollux_windy" error and assumed I was wrong. I downloaded the pollux version, and flashed it. That was the dumbest thing I did. I booted and immediately started looping at the cyanogenmod screen.
3) I attempted to troubleshoot by flashing firmware and kernels through Flashboot. It made it worse and now I cant get into recovery at all.
Here is the positives
I can connect to the device through Flashmode and Fastboot.
What should I do next to remedy this situation?
TheShackSpecialist said:
Hi everyone,
I would like to preface with I made some very stupid mistakes late last night/early this morning. I decided at around 11pm I was going to root and install a custom recovery on my SGP311. I followed this guide exactly to obtain root and recovery and it worked PERFECTLY.
http://forum.xda-developers.com/xperia-tablet-z/development/root-sp321-ftf-10-5-1-0-283-t2873377
Then the mistakes started happening. First mistake I made.
1) Instead of backing up everything in recovery I just Wiped everything. I deleted cache, davlik cache, system, and data. I thought at the time no big deal ill just flash a rom.
2)I decided to flash a CM nightly and I got the "your device is a pollux and this rom is for pollux_windy" error and assumed I was wrong. I downloaded the pollux version, and flashed it. That was the dumbest thing I did. I booted and immediately started looping at the cyanogenmod screen.
3) I attempted to troubleshoot by flashing firmware and kernels through Flashboot. It made it worse and now I cant get into recovery at all.
Here is the positives
I can connect to the device through Flashmode and Fastboot.
What should I do next to remedy this situation?
Click to expand...
Click to collapse
I just quickly read your post from work but since you wiped it and can no longer boot your tablet...just flash back a stock FTF with FlashTool and your tablet will back to full stock...you'll have to re-root obviously. Hope this helped... :good:
Crash338 said:
I just quickly read your post from work but since you wiped it and can no longer boot your tablet...just flash back a stock FTF with FlashTool and your tablet will back to full stock...you'll have to re-root obviously. Hope this helped... :good:
Click to expand...
Click to collapse
I'm downloading the FTF right now, Ill let you know how I make out so that people can see the resolution!
*EDIT* IT WORKED!!!! I missed the simple solution because I am so tired right now. But my tablet is working which is the important part THANK YOU!!!!