Related
Has anyone tried to root their i9023 with 4.0.4 using doomlord's easy rooting toolkit? http://forum.xda-developers.com/showthread.php?t=1321582
I tried it when I had 2.3.6 and it worked perfectly but want to update to 4.0.4 now.
If doomlord's doesn't work, is there any similar one click rooting? Also, when I rooted, it didn't erase my data and apps. Will that be the same? Thanks
I guess not. Been searching and couldn't find a non-destructive one and one as a simple click without needing cwm.
There's none that I am aware of. However, it's not really that complicated to flash the right SU zip, and if you don't want to flash cwm you can simply fastboot boot cwm.img and it will leave stock recovery intact and ready after you flashed everything.
Sent from my Nexus S using XDA
Couple things if you're already rooted on gingerbread do a nandroid back up. Put that and anything else you want to keep on your computer. Unlock the bootloader and restore your backup and update.
Stop messing around and unlock the bootloader.
albundy2010 said:
Couple things if you're already rooted on gingerbread do a nandroid back up. Put that and anything else you want to keep on your computer. Unlock the bootloader and restore your backup and update.
Stop messing around and unlock the bootloader.
Click to expand...
Click to collapse
How can he do a backup if the bootloader is locked = no cwm recovery? He's out of luck. Best thing he can do is backup the SD card and that's it. The rest is lost
Edit: failed to read sorry. Didn't notice the gingerbread part. Anyway if he's on stock and one clicked rooted he still doesn't have cwm so he can't make a nandroid, he can use titanium backup and save apps and data.
Sent from my
( •_•)
( •_•)>⌐■-■
Nexus S
(⌐■_■)
YYYYYYYEEEEEAAAAAAAAAAHHHHHHHHHHHH
If he is stock rooted he can flash cwm in the os. Either through rom manager or terminal
albundy2010 said:
If he is stock rooted he can flash cwm in the os. Either through rom manager or terminal
Click to expand...
Click to collapse
I thought that locked bootloader prevented the flash of any kind of unsigned .img even if you have root.
Guess i was wrong ;D
That's what you get when your first step with an android phone is unlock the bootloader
Not a one size fits all. Some phones all you need is root to flash a custom recovery and roms/kernels.
Others it can be a mess. Like the HTC g2 or even now the one x on att. Got the entire s on/ s off encryption nonsense and so on.
DeuXGod said:
I thought that locked bootloader prevented the flash of any kind of unsigned .img even if you have root.
Guess i was wrong ;D
That's what you get when your first step with an android phone is unlock the bootloader
Click to expand...
Click to collapse
He can flash a new recovery through the OS if he has root access only. Unlocked bootloader only provides fastboot support.
If you are fully stock (bootloader, recovery, no su), the only current way to root 4.0.4 is to have an unlocked bootloader.
albundy2010 said:
Not a one size fits all. Some phones all you need is root to flash a custom recovery and roms/kernels.
Others it can be a mess. Like the HTC g2 or even now the one x on att. Got the entire s on/ s off encryption nonsense and so on.
Click to expand...
Click to collapse
Yeah that's what make my confusion. My old HTC Magic needed unlocked bootloader to flash a recovery.
Harbb said:
He can flash a new recovery through the OS if he has root access only. Unlocked bootloader only provides fastboot support.
If you are fully stock (bootloader, recovery, no su), the only current way to root 4.0.4 is to have an unlocked bootloader.
Click to expand...
Click to collapse
Yeah about that i was pretty sure you needed unlocked bootloader, but about CWM flash i was convinced that you needed also unlocked bootloader, but as stated above, it's just for some devices.
Thank to all that responded. All this talk just flew over my head ... guess that's what I get for using simple one clicks
Let me try to straighten some stuff out.
How would I use titanium backup?
Do I titanium backup while it's still on gingerbread or after I OTA the ics 4.0.4?
Edit: duh! I can't use Ti backup after OTA ics because phone not rooted yet.
After backing up with Ti, I thought any attempt to root will erase all. Does the Ti backup not get erased?
Ti backup only backs up my app and the data to those apps, not how I customize my homescreen's widgets and notification bar, right?
So, I would have to do all that stuff over?
If I don't want to unlock bootloader or install cwm, any way to root and leave stock recovery intact?
Lazer Bear posted "if you don't want to flash cwm you can simply fastboot boot cwm.img and it will leave stock recovery intact and ready after you flashed everything."
Is that possible and how do I do it? Does that erase everything too?
Thanks to all!
bump
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
I heard there are problems flashing stock rom with CWR if the stock recovery isnt removed? Thats why I dont know if I should flash the stock image.
Is the process of flashing rom with CWR recovery the same as with stock recovery?
My phone is the i9023.
Thanks a bunch in advance.
Gambler_3 said:
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
Is the process of flashing rom with CWM recovery the same as with stock recovery?
Thanks in advance.
Click to expand...
Click to collapse
Baseband version? under about phone
billchen0014 said:
baseband version? Under about phone
Click to expand...
Click to collapse
i9023xxki1.
Sorry should have specified my phone in the OP.
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
You suppose thats better to do manually so I will have latest version of recovery and superuser?
And yes I am aware of the data loss waited sometime to finish all my games now I am ready to lose all my app data.
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
Do it this way. The one click is fine but using Android SDK and going through all that will help you in the long run. This way you know the process in case something goes wrong. It may be confusing at first but worth it. It will teach you a lot more than flashing a one click!
I learnt a lot from this and feel much more experienced and capable because of it. I know I will be able to solve any major issues using Android Debug Bridge (adb).
Okay then I am gonna try the manual way and gonna take out time for it. Now I just need to know what do I flash once I have unlocked bootloader and installed CWR?
I just want the stock google rom and receive OTA if nexus S continues to be supported by google.
You won't need to reinstall the ROM if you are currently on 4.0.4. The ROM stays there as-is. Feel free to do your wipes in recovery and reflash stock 4.0.4 through CWM if you must. You flash CWM to your phone and then superuser through CWM.
Steps:
Setup ADB/fastboot
Bootloader --> fastboot oem unlock --> agree
Bootloader --> fastboot flash recovery recovery.img --> this will give you CWM
Recovery --> flash superuser.zip and, if you must, wipe and reflash ICS (flash su AFTER this if done)
Reboot --> bingo
Also note, with stock ROMs it will replace your current recovery with stock recovery on each boot. If you want to keep CWM, delete /system/etc/flash-recovery.sh when you first boot. You'll have to reflash recovery afterward and it will stick.
Oh I was of the impression that unlocking bootloader wipes everything means it wipes the OS as well. That is nice if it's just data and not the OS, dont think I would reflash it if it's not needed.
Can you explain what you mean by will have to reflash recovery? I will have to do that even if I delete that file on first boot? And whats the drawback if I dont delete that file and stick with stock recovery?
As soon as you boot into stock android it will replace the recovery. So if that file is there on first boot, it will replace it while booting and you will be without CWM (stock instead). After first boot you can delete the file (you can reflash a ROM which has this deleted, or delete it yourself from a stock ROM, or even use adb or a recovery-based file manager to delete the file, then you won't have this problem at all) and it will no longer reflash stock recovery, but you would already have the stock one and need to flash CWM one more time to get it to stick. Easiest way is to just flash CWM and delete it within android imo, saves mounting commands and the such.
No downside really. If you need to flash something for one reason or another you'll just have to reflash CWM before you do so. Once rooted, ROM Manager can do this for you within android anyway.
I had already downloaded and installed the drivers from the one click root thread and my computer shows the android adb thing when I connect my phone with USB debugging.
But as you guys suggested I am gonna do the manual way. So do I just skip the installing driver on computer in the part 1 of this guide?
http://forum.xda-developers.com/showthread.php?t=1007782
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Gambler_3 said:
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Click to expand...
Click to collapse
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
DeuXGod said:
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
Click to expand...
Click to collapse
He has the i9023 to my knowledge. It is completely normal, though. Bootloader and recovery for i9020 and i9023 series are the same, this can be attributed to the issue with 4.0.3 recovery backlight not turning on.
If fastboot recognises your phone in the bootloader (the fastboot menu), your drivers are installed an working perfectly.
Finally got to the unlock bootloader screen, didnt do it just yet but now I know how to do it.
I must say the guide is a bit outdated, the software has changed quite a bit seems. The most frustrating part was that the fastboot file is actually in the platform tools folder instead of the tools folder which I didnt figure for a while. I will hold off rooting when I have a whole day off because once I lose everything I would be very anxious to get my phone back to normal which will take time.
Thanks for the help harbb, if I have any problem flashing recovery and superuser I will come back for more help.
And yes I have the LCD version i9023.
Btw the guide said the fastboot will be in the tools folder but the tools folder had a read me that "adb has moved to the platform tools folder" this is how I figured to go to that folder and thats where the fastboot file actually was.
Now it says I should put the recovery image in the tools folder so should I do that or put it in the platform tools folder?
In the instructions for the flashing recovery I am not understanding one thing.
6 - Then back on the SNS select Power Off (Reboot also works)
Part 4 - Root
1 - Power ON the SNS
So after flashing recovery I have to reboot? Since I am on stock rom that would bring back the stock recovery so how would I flash superuser then?
If I delete the stock recovery can I still get OTA updates?
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Harbb said:
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Click to expand...
Click to collapse
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Gambler_3 said:
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Click to expand...
Click to collapse
Good work, been wandering what you were up to on this
Hope you enjoy the possibilities.
I'm as happy as anyone else with this new method of unlocking the bootloader. I'm rooted the ODIN way and then have bean's stock rom with imosey's custom rom installed (via the k-exec). I've read that people are doing this with all different kinds of rom and recovery.
My question: what happens to the k-exec? All gets re-written? we don't need to go to stock to get this to work? It seems to me that it would be safer if we re stock, no?
I know there is a one click now but I prefer manual stuff.
I was wondering the same thing. I want to flash an kexec kernel but idk what might happen now that I'm unlocked
Sent from my SCH-I535 using xda app-developers app
vx2ko said:
I was wondering the same thing. I want to flash an kexec kernel but idk what might happen now that I'm unlocked
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You should be fine assuming you still have a kexec compatible recovery. Eventually all roms will move to full unlocked so kexec will pretty much be a thing of the past.
PJnc284 said:
You should be fine assuming you still have a kexec compatible recovery. Eventually all roms will move to full unlocked so kexec will pretty much be a thing of the past.
Click to expand...
Click to collapse
So running this new unlock method can be accomplished with K-exec on the phone? I've always thought that k-exec was a bott=strap kind of a method. Wouldn't this get messed up with this new method?
loveubuntu said:
So running this new unlock method can be accomplished with K-exec on the phone? I've always thought that k-exec was a bott=strap kind of a method. Wouldn't this get messed up with this new method?
Click to expand...
Click to collapse
I'm on Synergy 1.7 (non-nightly) and it's running fine. Still using the stock kernel and not Imo's lean kernel but it apparently still worked for others.
PJnc284 said:
You should be fine assuming you still have a kexec compatible recovery. Eventually all roms will move to full unlocked so kexec will pretty much be a thing of the past.
Click to expand...
Click to collapse
We need a list of non kexec and kexec recoveries and kernels. I've been in the Rom flashing and troubleshooting game for a while but never had to use a locked otloader so this kexec stuff is new. If someone could clarify what's kexec and what's not that would be great
Sent from my SCH-I535 using xda app-developers app
loveubuntu said:
I've always thought that k-exec was a bott=strap kind of a method. Wouldn't this get messed up with this new method?
Click to expand...
Click to collapse
To the best of my knowledge, when the bootchain gets to the boot partition, it loads the kernel on boot.img. It then proceeds to start up the system partition. If you're using kexec, the ROM you're using checks whether the kernel is the expected one or stock. If it isn't the right one, it reboots to recovery, passing instructions to CWR on what to do when it gets there (please feel free to correct me on that part, my knowledge there is vague). That's the first reboot. Once in recovery, those instructions tell recovery to load the right kernel into memory and uses kecex to perform a hardware restart and boot from the kernel it just put in memory. That's the second reboot you see. Once that kernel is loaded up, it starts up the system partition and finishes booting into your ROM.
Before, if the image on boot did not match what the bootloader would permit, it would throw an error and refuse to boot. Unlocking the bootloader allows us to put whatever we want on boot. What got overwritten when you unlocked your bootloader was aboot, the part of the boot sequence that's loaded before the boot partition. If you install a rom that includes a boot.image, now it will just boot from that with whatever kernel. It boots normally, the rom no longer needs to reboot into recovery to load the correct kernel, and all of that kexec infrastructure, which is still there goes unused.
So as long as you don't switch to a recovery without kexec support, you can flash whatever you want, kexec, stock, or using the unlocked bootloader. You can't get yourself into any trouble restoring a backup can't fix.
Of course, if you were to switch to TWRP or another recovery not supporting kexec and then try to boot a kexec rom, you're asking for a bootloop. So stick with the recovery you're using now until every rom or kernel you'd possibly try no longer uses kexec.
lazarus2405 said:
To the best of my knowledge, when the bootchain gets to the boot partition, it loads the kernel on boot.img. It then proceeds to start up the system partition. If you're using kexec, the ROM you're using checks whether the kernel is the expected one or stock. If it isn't the right one, it reboots to recovery, passing instructions to CWR on what to do when it gets there (please feel free to correct me on that part, my knowledge there is vague). That's the first reboot. Once in recovery, those instructions tell recovery to load the right kernel into memory and uses kecex to perform a hardware restart and boot from the kernel it just put in memory. That's the second reboot you see. Once that kernel is loaded up, it starts up the system partition and finishes booting into your ROM.
Before, if the image on boot did not match what the bootloader would permit, it would throw an error and refuse to boot. Unlocking the bootloader allows us to put whatever we want on boot. What got overwritten when you unlocked your bootloader was aboot, the part of the boot sequence that's loaded before the boot partition. If you install a rom that includes a boot.image, now it will just boot from that with whatever kernel. It boots normally, the rom no longer needs to reboot into recovery to load the correct kernel, and all of that kexec infrastructure, which is still there goes unused.
So as long as you don't switch to a recovery without kexec support, you can flash whatever you want, kexec, stock, or using the unlocked bootloader. You can't get yourself into any trouble restoring a backup can't fix.
Of course, if you were to switch to TWRP or another recovery not supporting kexec and then try to boot a kexec rom, you're asking for a bootloop. So stick with the recovery you're using now until every rom or kernel you'd possibly try no longer uses kexec.
Click to expand...
Click to collapse
Thank you, great explanation. To clarify: If you have k-exec and rot before the bootloader unlock leak and now unlock your bootloader with the new leak, you have the best of both worlds. If you use a ROM that uses K-exec, the k-exec part kicks in and if you use the new CM10 alpha without k-exec, the k-exec is unused and the new unlock bootloader is utilized.
Is that right?
Folks...listen up! You can unlock your device on any rom. That being said now that your unlocked, kexec or non kexec kernels will work on a unlocked device. Just make sure your unlocked and using cwm 6.0.1 and everything thats currently available to flash on our device will work. Kexec is not some majical program where we need to worry about bricking our device. Its simply a script that hijacks the boot process after the stock kernel passes verification and then it side loads the custom kexec kernel off of the recovery partition. Unlocking the bootloader has no effect on any of this. Im still using imoseyons 12-2 kexec kernel with beans 8 and the only difference is the device boots up alot quicker. Reason being the bootloader is no longer checking for signed software. Its really no big deal folks..everything still works the same.
droidstyle said:
Folks...listen up! You can unlock your device on any rom. That being said now that your unlocked, kexec or non kexec kernels will work on a unlocked device. Just make sure your unlocked and using cwm 6.0.1 and everything thats currently available to flash on our device will work. Kexec is not some majical program where we need to worry about bricking our device. Its simply a script that hijacks the boot process after the stock kernel passes verification and then it side loads the custom kexec kernel off of the recovery partition. Unlocking the bootloader has no effect on any of this. Im still using imoseyons 12-2 kexec kernel with beans 8 and the only difference is the device boots up alot quicker. Reason being the bootloader is no longer checking for signed software. Its really no big deal folks..everything still works the same.
Click to expand...
Click to collapse
Quick noob question. I rooted and flashed synergy v1.7 using ROM Manager from the app store. When I open the app is says rom manage v5.0.1.5 at the top. Everything is running perfect and do not want to flash a new rom until synergy does a jellybean rom. Should I use the unlock app to unlock my phone now or is there no need? Also is rom manager ok to continue using or should I use something else? Thanks for the help
I got lazy and unlocked using the market app. Running Bean building 8 that is using kexec. I'm still getting three reboots. Is this right?
Sent from my SCH-I535 using xda premium
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
confusedman112 said:
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
Click to expand...
Click to collapse
What methode did you use to unlock it? I'm running the stock no nonsense rom and I belive unlocked with no problems
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
lazarus2405 said:
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
Click to expand...
Click to collapse
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
Click to expand...
Click to collapse
Install EZ-Recovery from the play store and flash 6.0.1.0?
PJnc284 said:
Install EZ-Recovery from the play store and flash 6.0.1.0?
Click to expand...
Click to collapse
Thanks. Flashing Synergy now to test it...let's see what happens.
EDIT: Flashed just great, but still isn't working. But, it's cool, CM10 mods work and I got what I needed (exported Verizon contacts and improted them to Google Contacts using My Verizon's webstie)
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x.
Click to expand...
Click to collapse
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
lazarus2405 said:
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
Click to expand...
Click to collapse
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
droidstyle said:
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
Click to expand...
Click to collapse
Because I am at work and don't have time to find and locate? Could you reference it, please?
PJnc284 said:
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
Click to expand...
Click to collapse
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
newuser134 said:
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
Click to expand...
Click to collapse
Just to be safe. Wanted to get rid of the sprint related elements from the original root so I Odin'd back to stock with cwm installed using the VRALF2 tar found here. Tried to boot into recovery to factory reset prior to first boot and had 0 recovery (not stock nor cwm). Luckily the rom booted and I used the simple root method to root and install EZ-Recovery to install CWM.
If I flashed synergy v1.7 and used rom manager v5.x.x and then unlocked the boot loader how would I flash a new rom? Do I have to use ez recovery with clockwork mod v6.x.x since it is now unlocked or can I continue using rom manager with clockwork mod 5.x.x. I'm a noob and won't be looking to switch roms until synergy gets jellybean. Thanks for the help and hopefully I made sense with my question
synergy to beans to synergy bootloop
I think my issue might be related to the issues stated above.
So after after having unlocked my bootloader with EZ unlock & installing beans custom Rom via TWRP , I decided to go back to synergy. I made a nandroid of my synergy which was origianlly installed with CWM and figured I could just wipe and restore that with TWRP. Total bootloop.
OK, so I pulled the battery, tried it again...bootloop.
SO I pulled the battery, wiped and installed the synergy zip thinking I could try a fresh install. I got a message in TWRP that E:sd-ext was not found, but wipe seemed to happen so I continued the process.
installation said it was successful but now when I try to boot up, I either get stuck in the android is upgrading applications (looping over and over) or it gets through there and tells me all teh com.android.xxxx applications unexpectedly stop.
is this a soft brick? can I recover from this? are there incompatibilities between the kernels of bean's custom rom and synergy for verizon samsung galaxy s3?
right now when I enter wipe in TWRP, I see ext_data and ext_system and dock_sdcard.
how can I remove these?
I found this guide:
[MOD] Data2SD (Enhanced) - I/O Fix
Uninstallation
Don't like data2sd? Just flash a non-data2sd kernel using recovery and when you boot back into Android your /data will be on the internal storage. This could also be accomplished by flashing your ROM on top of itself without wiping.
Troubleshooting
1) Grab the mount-data2sd.zip from the second post.
2) Boot into TWRP and flash the mount-data2sd.zip. This will mount the microSD as /data in recovery. It will allow us to wipe it, format, etc using recovery.
3) Wipe "Internal Storage". This will erase the entire ext4 partition on your microSD.
4) Flash ROM
5) Flash data2sd kernel for ROM
Click to expand...
Click to collapse
except the data2sd kernerls are no longer available
I tried cromi-3.2.x-data2sd.zip and it says zip is corrupt.
Also I think I no longer have root, I tried asus unlock tool and it could not install. Do I need to be in the stock rom?
I install super user but it says I have to unlock my device.
You need to slow down and stop trying stuff willy nilly. Could be dangerous...
Stop trying to unlock the tablet, you are already or you wouldn't have TWRP.
Forget about root - it's immaterial here.
What's your bootloader, recovery and Rom version? Should be easy to find a kernel or rom you can flash once we have that info.
Sent from my Nexus 5X using Tapatalk
thanks
using:
twrp_tf700t_kang_2.8.7.4
flashed this bootloader:
https://forum.xda-developers.com/showpost.php?p=40623406&postcount=1997
newly installed rom:
omni-6.0.1-TF700t_zombi_KANG_RELEASE_signed
I hear you about being more careful. Though speaking of silly,I tried the wipe data from bootloader
prior I couldn't get fastboot devices to work from cmd, after I could. I took the risk only because its an older device (bad reason since it's still super useful).
Was also not able to just drag drop files from pc into tf1700 prior to wipe. < this happened after I had done a factory reset/ tried to do a reformat.
This came in handy too:
fastboot -i 0x0b05 erase userdata
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Click to expand...
Click to collapse
I cannot remember what bootloader that was and if dasunsrule modded it. Boot into fastboot and post the version number. It's among the small script on the screen with 3 icons
Sent from my Nexus 5X using Tapatalk
Android cardhU-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Paprika88 said:
Android cardhU-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Click to expand...
Click to collapse
Man! That bootloader is ancient! JB something from 2013 or so....
Ok, so first you have to flash a recovery that is compatible with your current bootloader so that you don't brick this thing.
Go here, download TWRP 2.5.0 and flash it in fastboot. https://dl.twrp.me/tf700t/
Boot into TWRP and make sure you are running the correct version.
Then go here, download the 10.6.14.10 bootloader/recovery package and flash it in recovery: https://forum.xda-developers.com/showpost.php?p=55238386&postcount=3
Reboot to recovery.
I know, it might be tempting to just flash the 10.6.1.14.10 bootloader from that post, right? Should get you to the same place without first flashing TWRP 2.5, no? Except that I would not flash anything with a recovery that is not compatible with the currently installed BL. And especially not a bootloader, which is always risky!
Ok, now you're back to TWRP 2.8 but this time with the correct bootloader.
If I were you, I would update TWRP to the latest version by flashing 3.1.0 in fastboot - but that's your choice.
In either recovery you then should: a) format /data, b) convert /data to f2fs, c) flash a KatKiss rom
a) + b): https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
c): https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Alternatively you could flash the 10.6.1.14.10 Asus stock blob in fastboot which would put you back on a stock system with the latest bootloader, then flash TWRP 3.1.0 and then format and convert /data and flash the rom. Either method works fine...
And if you do not know how to flash in fastboot you really should study this: https://forum.xda-developers.com/showthread.php?t=2688891
Good luck!:good:
All done. Everything is running smoothly, thanks in great part to your comprehensive guide.
Ill go over more in detail how it all went later.
The format took quite a while and had a bit of issue trying to copy new rom from PC into tablet.
Btw for all I know I might of had latest bootloader before I flashed the old one.
Couldn't find the sticky for latest bootloaders
I still see micro and docked sd card as wipe options, those are defaults?
ext_data and ext_system are now gone, i guess I had tried to do ROM2SD if I had ext_system
Sent from my TF700T using Tapatalk
Good deal. Congrats
Yep formatting in TWRP rakes an hour or so, but you don't have to do it too often.
Don't understand "sticky for latest bootloader"?
If you have the .10 you have the latest.
If you have docksd available in TWRP means you gave the Kang version, the only one supporting the dock storage.
It's not the default - just available...
Sent from my Nexus 5X using Tapatalk
i see explains why the twrp 2.5 didn't have the sddock
by sticky i meant sticked thread/or from the ressource/guides...