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
Related
I'm fairly new to the whole rooting business, and got my phone rooted the first day I had it and customized it how I wanted. Now I want to wipe it to try some new stuff. I've already backed everyone up with Titanium Backup and made a Nandroid recovery, but when I performed a factory reset/data wipe, I reset my phone and it still loaded my rom (the dasBAMF 3.0). Since I wiped but my Rom loaded (my assumption at least) something isn't working correctly and my keyboard won't pop up when I need to type in text for anything. Did I miss a step to completely wipe my phone...?
EDIT***
Really, I just want to try and get my phone either back to stock, or as close as I can (since I don't know what they check for when trying to exchange at the verizon store, if possible) so that my warranty is voided and stuff....
Yeah... You missed the who step of flashing another ROM. It's going revert back to the last ROM that was there if it isn't replaced.
Oh :/ Where would the vanilla TB rom be? Cause I might just be missing it, but I can't seem to find it in Android Development.
I would prefer to exchange it for another phone, so I'm trying to get it back to stock (or as close to it as I can if all they do is look at it without checking so I can exchange).
You're gonna want what's called an RUU. I'm not sure where the most recent OTA RUU is or who's been taking care of those. It should be in the dev forum. The version number should start with 1.70. To flash it, change the name to pg51img.zip and flash it like you would a radio. It will snap your phone right back to factory stock. If you can't find it, let me know and I'll try to hunt it down.
There's this:
http://forum.xda-developers.com/showthread.php?t=997724&highlight=RUU
but none of the file names start with 1.7? Also, the TS has in caps red: "DO NOT FLASH THESE OVER ROOTED DEVICES, UNLESS YOU KNOW WHAT YOU ARE DOING." and I wouldn't know what to do with it even if I got the RUU that started with 1.7.
EDIT***
Well, I found this:
http://forum.xda-developers.com/showthread.php?t=1009423
Since I'm new, that will work for me too, correct? I see nothing stating that it shouldn't...
iImmortality said:
There's this:
http://forum.xda-developers.com/showthread.php?t=997724&highlight=RUU
but none of the file names start with 1.7? Also, the TS has in caps red: "DO NOT FLASH THESE OVER ROOTED DEVICES, UNLESS YOU KNOW WHAT YOU ARE DOING." and I wouldn't know what to do with it even if I got the RUU that started with 1.7.
EDIT***
Well, I found this:
http://forum.xda-developers.com/showthread.php?t=1009423
Since I'm new, that will work for me too, correct? I see nothing stating that it shouldn't...
Click to expand...
Click to collapse
That last link, got to restore to stock for root and non-root users... That will work. Basically, after you flash the first one you'll be stock without root. The second flash will restore S-on.
I recently got my replacement EVO3D, rooted it, and flashed SteelRom 1.04. I noticed that my phone randomly "crashed" (for lack of a better word) and, while trying to reboot, became trapped in a never-ending boot loop cycle. Only temp solution was to do a battery pull, which allowed me to boot back into the ROM.
Assuming that it was a problem with the ROM, I tried flashing CleanROM 1.3. The same problem occurred (esp. when I was browsing the web). Worse, even, because even a battery pull didn't fix it.
I nandroided back to Stock rooted to see if the problem remains.
So, besides the simple sharing of my problem, I'd like to know if
Can I reroot after "Complete Stock and S-ON"?
Is this problem stemming from ROM bugs, or maybe is it a hardware defect?
I am still within the 30 days, but I have already had it exchanged once. What should I do?
Thanks will be given to those who help
EDIT: I went back to Stock/S-ON and rerooted. Problem fixed for now
Did you notice this problem before you rooted? If not, then something probably went wrong during the ROM flashing process.
I doubt its the ROM itself otherwise I'm sure there would be plenty of folks posting the issue in the ROM's thread. Likewise, if you didn't have the problem before you rooted, its not a hardware issue either.
A couple of questions:
1. Did you wipe your caches before flashing the ROM?
2. Did you try performing a factory reset after you flashed the ROM and started
having this issue?
mvansomeren said:
Did you notice this problem before you rooted? If not, then something probably went wrong during the ROM flashing process.
I doubt its the ROM itself otherwise I'm sure there would be plenty of folks posting the issue in the ROM's thread. Likewise, if you didn't have the problem before you rooted, its not a hardware issue either.
A couple of questions:
1. Did you wipe your caches before flashing the ROM?
2. Did you try performing a factory reset after you flashed the ROM and started
having this issue?
Click to expand...
Click to collapse
Hi, and thanks for your reply.
I rooted the phone as soon as I got it (maybe stock for 15 minutes) so I didnt have a chance to observe this problem then.
I rooted using Revolutionary 0.4a I flashed SteelRom and CleanROM, both of which showed this problem. I finally flashed ShooterRewind 3D, which hadn't shown this problem until I tried to reply to this thread, ironically.
and to answer your questions:
I do. Actually I always use t3_superwipe_1.3.zip before flashing.
I also tried to "Wipe Data/Factory Reset" after I experienced the problem. No change.
Finally, can you tell me if I can go back to stock using one of the guides and reroot using Revolutionary?
Yes you can go back to stock and back to S-ON. There is a thread in the dev section that will guide you.
http://forum.xda-developers.com/showthread.php?t=1194053
nevermind, did not read OP fully.
mvansomeren said:
Did you notice this problem before you rooted? If not, then something probably went wrong during the ROM flashing process.
I doubt its the ROM itself otherwise I'm sure there would be plenty of folks posting the issue in the ROM's thread. Likewise, if you didn't have the problem before you rooted, its not a hardware issue either.
A couple of questions:
1. Did you wipe your caches before flashing the ROM?
2. Did you try performing a factory reset after you flashed the ROM and started
having this issue?
Click to expand...
Click to collapse
mvansomeren said:
Yes you can go back to stock and back to S-ON. There is a thread in the dev section that will guide you.
http://forum.xda-developers.com/showthread.php?t=1194053
Click to expand...
Click to collapse
tatnai said:
nevermind, did not read OP fully.
Click to expand...
Click to collapse
Thanks Everyone for you're replies. I went back to Stock S-ON, talked with Sprint, they did a ##786# Reset, and then I rerooted with Revolutionary. No problems so far, although Revolutionary did an odd root sequence:
Code:
Rebooting to fastboot
Rebooting to fastboot (again)
Rebooting to fastbook (yet again)
Communications with the device were interrupted, try again
Anyway, I am all set now, so thank you all. Appreciate it.
I was running the Spike Pure ICS on my SGS2, before which I had the ICS version of MIUI. I tried flashing Lite'ning Rom 3.6 through Odin, but was unsuccessful. Also, that's time I noticed the 7.2 version of CM and decided to flash that and that's when the problem occurred.
Although I could flash CM 7.2 properly and could also install the GApps through CWM, on rebboting it through the CWM, my phone got stuck and it wouldn't go into Recovery any more.
Luckily, it would boot into Download Mode and I could flash the stock rom through Odin and get my phone back to stock, thereby losing the Root and CWM.
I wanna know as to what could cause such an issue to arise. so that I can prevent it later!
Your help and time are appreciated!!
Why start a 2nd thread ?
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
And you couldn't make another post to your initial post along the lines of 'Why did this occur in the first place ?' You could even easily change the title of your initial thread to reflect your desire to know the answer to this question.
One of the main rules of XDA is don't spam.
I'm extremely sorry if I've spammed as it wasn't my intention at all!
This thread was and still is a genuine question which I want to know!!
Also, could you please tell me about the occurrence of such a problem on my phone??
gadgyfreak said:
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
Click to expand...
Click to collapse
I think answer was there but might be not clear......
When you flash gb over ICS you have to wipe, when you mix stuff after that, meaning trying different kernels to fix the issue it might get worse.
Because recovery is somewhat linked to kernel in s2, you won't get recovery in a messed up system.
So when you flash a complete firmware using Odin and then do data cache wipe, it get fixed.
Hope this helps.
But then how is it possible that my phone didn't get all messed up when I flashed CM 9(Nightly) over my pre-existing CM 7.1, while it happened when I tried it vice versa?
already told you, when you go from ICS newer kernel to GB older kernel, wipe is necessary. Going from GB to ICS will work but wipe is better there too.
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Flash a GB rom.
gadgyfreak said:
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Click to expand...
Click to collapse
save data
Wipe dial *2767*3855#
Flash GB Rom, preferably stock using Odin.
Should boot now, if not go into recovery and wipe data cache.
It will boot now.
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.
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.