Related
I searched this forum a bit and I can't find a nice guide. I am currently running rooted .19 on my TF101, B70KAS. Is it as simple as dropping the ROM on my internal SD and letting it update to the latest Revolver release (based on .21)? Or can I do it with booting into recovery mode? This is my first tablet and I have no clowworkmod on my tablet... do I need to flash that somehow? Where's a guide?
thanks!
ninjai117 said:
I searched this forum a bit and I can't find a nice guide. I am currently running rooted .19 on my TF101, B70KAS. Is it as simple as dropping the ROM on my internal SD and letting it update to the latest Revolver release (based on .21)? Or can I do it with booting into recovery mode? This is my first tablet and I have no clowworkmod on my tablet... do I need to flash that somehow? Where's a guide?
thanks!
Click to expand...
Click to collapse
Since i am firm believer you need to learn what you are doing i will lay down the basics from there you are on your own.
1) read and study SU access
2) read and study SU access
3) read and study SU access
4) root
5) install clockwork recovery
6)download Revolver
7)verify the MD5SUM
8)boot into recovery
9)do a nandroid back up
10) do a factor reset via CWRI
11) flash the OS you want
12) reboot
13) enjoy
neidlinger said:
Since i am firm believer you need to learn what you are doing i will lay down the basics from there you are on your own.
1) read and study SU access
2) read and study SU access
3) read and study SU access
4) root
5) install clockwork recovery
6)download Revolver
7)verify the MD5SUM
8)boot into recovery
9)do a nandroid back up
10) do a factor reset via CWRI
11) flash the OS you want
12) reboot
13) enjoy
Click to expand...
Click to collapse
I am very familiar with CWM, flashing, nandroid backups, etc. I've had a nexus one for a long long time. I just can't find any good stickies on how to install CWM on my tablet, which I assume is my first step, though I find it odd there are no stickies. On the Nexus One forum there are lots! Where can I learn about installing CWM on my tablet with stock (but rooted) .19 FW?
ninjai117 said:
I am very familiar with CWM, flashing, nandroid backups, etc. I've had a nexus one for a long long time. I just can't find any good stickies on how to install CWM on my tablet, which I assume is my first step, though I find it odd there are no stickies. On the Nexus One forum there are lots! Where can I learn about installing CWM on my tablet with stock (but rooted) .19 FW?
Click to expand...
Click to collapse
Search for RecoveryInstaller in the Themes and Apps section.
One click CWM installer, don't get any easier than that.
I had the Same issue coming from the nexus s. the tricky bit is that rom manager does not support the transformer. I've got a galaxy tab 10.1 as well and flashing over a custom recovery was easy as pie.
anyway, what you have to do is this: http://forum.xda-developers.com/showthread.php?t=1213723
(http://forum.xda-developers.com/showthread.php?t=1093818)
then you need to install an app (i use reboot2recovery) from the marketplace to get into the custom recovery. i've tried quickboot or rom manager but all it does it take me to a black screen or reboot the device. reboot2recovery will actually drop you into clockworkmod recovery. from there, do your nandroid backup. you'll need an SD card in your transformer for it to actually go ahead with the backup.
aside: from my reading, the backup should backup to internal storage with that modded clockwork. i've never been able to get it to work though. anyway, just use an SD card for now so you can get through the difficult stuff.
so at this point uve done the following:
installed clockwordmod using the first 2 links and installed the reboot2recovery APK to get into recovery.
now you have an SD card in your transformer and you are doing a nandroid backup.
once completed, put the 200+mb revolver rom on the root of your SD card. you may also want to put another kernel. i use the one recommended by revolver.
now just wipe the cache, data, etc as usual. now flash the rom, reboot the system when completed. plug in your gmail account, wifi password etc. and then reinstall the reboot2recovery apk. now reboot to recovery and then flash the kernel. reboot and ure good to go. install revolver parts to allow for additional tweaking and OTA updating.
i got my transformer from bestbuy this thanksgiving and went to revolver 3.9.5 immediately. last night i actually flashed revolver 3.11 right over it. not a single problem.
edit: reading the above post, i remember that my FIRST recovery installation was using that one-click tool and, as was said, it works flawlessly. you still need the reboot2recovery though. and recoveryinstaller WILL NOT install the modified for internal storage version of clockwork. i'm thinking maybe i just havent tried backing up since updating to the internal storage version, which is why i think i've "never gotten it to work"
baseballfanz said:
Search for RecoveryInstaller in the Themes and Apps section.
One click CWM installer, don't get any easier than that.
Click to expand...
Click to collapse
Awesome, I had tried it earlier and it didn't do anything. Then I realized that my superuser app was FCing, however I could still use adb shell and su just fine! After I realized there was an update for the superuser app, I installed it. Everything is perfect now.
kramer987 said:
I had the Same issue coming from the nexus s. the tricky bit is that rom manager does not support the transformer. I've got a galaxy tab 10.1 as well and flashing over a custom recovery was easy as pie.
anyway, what you have to do is this: http://forum.xda-developers.com/showthread.php?t=1213723
(http://forum.xda-developers.com/showthread.php?t=1093818)
then you need to install an app (i use reboot2recovery) from the marketplace to get into the custom recovery. i've tried quickboot or rom manager but all it does it take me to a black screen or reboot the device. reboot2recovery will actually drop you into clockworkmod recovery. from there, do your nandroid backup. you'll need an SD card in your transformer for it to actually go ahead with the backup.
aside: from my reading, the backup should backup to internal storage with that modded clockwork. i've never been able to get it to work though. anyway, just use an SD card for now so you can get through the difficult stuff.
so at this point uve done the following:
installed clockwordmod using the first 2 links and installed the reboot2recovery APK to get into recovery.
now you have an SD card in your transformer and you are doing a nandroid backup.
once completed, put the 200+mb revolver rom on the root of your SD card. you may also want to put another kernel. i use the one recommended by revolver.
now just wipe the cache, data, etc as usual. now flash the rom, reboot the system when completed. plug in your gmail account, wifi password etc. and then reinstall the reboot2recovery apk. now reboot to recovery and then flash the kernel. reboot and ure good to go. install revolver parts to allow for additional tweaking and OTA updating.
i got my transformer from bestbuy this thanksgiving and went to revolver 3.9.5 immediately. last night i actually flashed revolver 3.11 right over it. not a single problem.
edit: reading the above post, i remember that my FIRST recovery installation was using that one-click tool and, as was said, it works flawlessly. you still need the reboot2recovery though. and recoveryinstaller WILL NOT install the modified for internal storage version of clockwork. i'm thinking maybe i just havent tried backing up since updating to the internal storage version, which is why i think i've "never gotten it to work"
Click to expand...
Click to collapse
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
jesesystem said:
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
Click to expand...
Click to collapse
It mean open your command prompt in your computer fire up the ADB server and type
Code:
adb reboot recovery
Why why not download the reboot recovery app from the market?
https://market.android.com/details?id=com.transformer.recovery
Sent from my Transformer TF101 using Tapatalk
jesesystem said:
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
Click to expand...
Click to collapse
Have you installed CWM recovery?
Rooting alone does not install CWM recovery.
jesesystem said:
none of those gives a step by step (im noob )
i just dont know what "Reboot into recovery using "adb reboot recovery" " means
im already rooted and i cant get to the CWM recovery because i cant see the install from zip, backup current rom or wipe data , nor those options
Click to expand...
Click to collapse
Search for RecoveryInstaller in the Themes and Apps section.
One click CWM installer, don't get any easier than that.
thank you guyz i just needed to install cwm recovery, its just that those steps are not on any step by step , i can access now in to cwm recovery
Once in recovery it cant mount sd
SGS Dutchie said:
Once in recovery it cant mount sd
Click to expand...
Click to collapse
You have a micro sd card insert into the slot?
baseballfanz said:
You have a micro sd card insert into the slot?
Click to expand...
Click to collapse
Nope,thought it was the internal sd just like is shown in file explorer.
SGS Dutchie said:
Nope,thought it was the internal sd just like is shown in file explorer.
Click to expand...
Click to collapse
CWM only work with external card for now
Removable/MicroSD
baseballfanz said:
CWM only work with external card for now
Removable/MicroSD
Click to expand...
Click to collapse
Ah, I must go and search for one then.
baseballfanz said:
CWM only work with external card for now
Removable/MicroSD
Click to expand...
Click to collapse
Thx man, you really helped me out today. First with my root/cwm problem and now with this rom.
You really are a great help. Thx again!
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
yuma80 said:
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
Click to expand...
Click to collapse
The problem with ROM Manager is that it messes up the files when flashing a ROM or any file. It is more advised to use CMW Recovery.
yuma80 said:
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
Click to expand...
Click to collapse
Rom Manager should not be used on the G2x. If you flash a rom and something goes wrong and you can not boot you are dead in the water. Use Nvidia CWM instead.
http://forum.xda-developers.com/showthread.php?t=1056847
Yes thanks. I understand that I shouldn't use ROM Manager, but I want to know what it does and why it doesn't work. For starters anybody know where it writes CWM to?
Worse comes to worse I'm just going to dump /dev/block/mmc* and look for strings or disassemble the apk or something...
yuma80 said:
Yes thanks. I understand that I shouldn't use ROM Manager, but I want to know what it does and why it doesn't work. For starters anybody know where it writes CWM to?
Worse comes to worse I'm just going to dump /dev/block/mmc* and look for strings or disassemble the apk or something...
Click to expand...
Click to collapse
I've always been curious about the details of a 'fake flash' too.. please let us know if you figure out any details.
Rom manager has been around since the original Droid from Verizon. The fake flash you refer to isn't actually a fake flash. It actually flashes CWM recovery. It just doesn't work on this particular phone. I may be wrong on the exact details but the G2x partitions and drivers require the use of NVflAsh to install the CWM. However, there are many phones that once they have been rooted, the user can install Rom Manager and use the Flash Recovery option to install their CWM recovery. There are also times when a particular recovery version (ie.. 5.0.5. Or 4.6.3) works better than another on one particular phone. Rom manager allows users an easy way of flashing between those CWM versions by simply pushing the flash button.
So in summary of a long response... it is only called a fake flash because it looks like it worked on our phone , but in fact it does not. We have to use NVflash to flash our recovery.
If it looks like I'm remotely right ( which I think I am..) hit that thanks button. (Shameless request, I know)
From my understanding, the "fake flash" that ROM Manager does is that it doesn't actually flash CWM like NVFlash does (on the recovery partition) but still puts the CWM files on your SD card saying that you do have it installed (sdcard/clockworkmod) so when you try to flash/install a ROM, it can't put it anywhere. I don't think it will flash anything, but people mess up their devices by wiping data/system and such...
OR...
Maybe it does flash CWM to your device but it has the partition tables all messed up?
One or the other lol, it's just a guess for both options but I believe the first one is right.
I've wondered for a while why rom manager is included in roms for the g2x when it's not advised to use it
Sent from this
DorisTheHeavy said:
I've wondered for a while why rom manager is included in roms for the g2x when it's not advised to use it
Sent from this
Click to expand...
Click to collapse
To rename your nandroid backups .
buru898 said:
To rename your nandroid backups .
Click to expand...
Click to collapse
I never thought about that. I was always unsure what flashing CWM with ROM Manager would do when it's already on my phone using NVFlash.
Since our phones have a dual partition in it. I think it flashes to the internal 1 gig memory so then loading another rom writes over it.
Sent from my LG-P999 using xda premium
OK, I finally had some time to do some poking around. Some of this is guess-work since I was too lazy to verify 100% exactly what it does when you specify that you're running a G2X.
Anyway, in it's settings DB it says this phone's recovery partition is read-only, and there's no flash command set, so I guess it doesn't try to flash it directly. It looks like it's relying on the Google stock recovery image to do the flashing instead, so it downloads a recovery-update.zip to the SD card and writes a script to /cache/recovery and reboots the phone into recovery mode. Google stock recovery would execute the script in /cache/recovery, which says to apply recovery-update.zip, but the actual stock recovery on the phone is either not Google stock, or has been modified; it doesn't bother to execute scripts, it just does a factory-reset (clear /cache, /data, etc) so that's why it doesn't work.
Meanwhile, ROM Manager writes to it's DB that it just flashed CWM version X.Y.Z and happily displays that every time it runs, even though that's not true.
I used NVFlash and moved on with my life.
I'll preface this by saying the following:
I know there are a lot of brick guides out there, and most are relatively easy to get out of. I've worked myself into a bit of a pickle, though.
It started when I noticed that there was an update available through the CM updater. I figured, what the hell, I'm running a nightly and this is likely to be a stable release, so I went ahead and downloaded it. I got home and checked the get.cm page, and sure enough, a new, stable build had recently been released. Being the diligent soul that I am, I made sure to do a full backup before I installed the .zip. Everything worked out just fine, the backup went swell, the update finished without problems, and then I rebooted my device.
All I see is the Asus splash screen. It just stays there. So I think, no big deal, it just didn't work out like I wanted, I'll go format my data (which I didn't do the first time around, in hopes that everything would carry over) and install again. The same thing happens. I haven't started panicking yet, since I still have 3 backups (1 older Jellybean, and one much older ICS). None of them work. I wipe everything that I can think might help. Data, system, cache, dalvik, you name it. Nothing was working, and I was starting to freak out. Then I decided to try to get some action through fastboot, hoping that I could push a .zip that wasn't the CM10 update that had started everything. In my search for a push command, I thought it would be a good idea to try a wipe from fastboot. This wiped everything. Not only the system, boot, etc. partitions, but also my personal partition that had all of my data. This in itself isn't a big problem, but it also left the partitions unformatted. Now I have a device that is devoid of data and can't do anything but get into CWM and fastboot.
What the hell can I do? Am I doomed? Is there no way to get out of the hole I've dug myself into?
tl;dr failed update, things got really real, really fast.
Specs before the initial update
ROM: CM10 nightly, Jellybean 4.1.x
CWM: 5.5.0.4
Kernel Version (?): 9.4.3.30-20120604 (I'm not sure with this, it says something about "android carhu-user" before it)
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
DerangedLoofah said:
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
Click to expand...
Click to collapse
That's the thing, though, I have no idea how I'm supposed to get it to my device now...
http://forum.xda-developers.com/showthread.php?t=1989076
Have you tried this? I was just thinking about it because I can't reflash my recovery and thought this may be the way to start over.
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Glad you got it!
nitsuj79 said:
Glad you got it!
Click to expand...
Click to collapse
DerangedLoofah managed to get it, but I still haven't had any luck.
DerangedLoofah said:
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
How did you flash it in fastboot? I can't figure out how to get to something that's on the external SD card. What were the exact commands you used?
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
nitsuj79 said:
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
Click to expand...
Click to collapse
Does that work with CWM? I don't have the stock bootloader on it.
This works only if you didn't flash custom recovery, it is the best method for locked devices. But you can still flash any stock ROM from CWM (but I suggest to use TWRP, you can install it from external sd). And you can push the ROM to internal memory via adb. I think you can install stock ROM via fastboot too, I am not sure, but the command fastboot update should help.
I managed to get it working again. If you can get to fastboot, push a bootloader that supports an external SD cards (like TWRP) and then from that install one of the official ASUS firmwares. From there, you have to root again, but it's better than having a device that won't boot at all.
I fragged up Android by applying an update, so I can't boot into Android.
I can get into CWM, but it doesn't see my backup... The backup is in /clockwordmod/backup/2013-03-17-14.09.00 . I can see it when I put my SD card in the PC.
However, CWM isn't finding it when it's in the device, and there's no option to direct CWM to where it is....
Solution anyone?
Bump....
damian5000 said:
I fragged up Android by applying an update, so I can't boot into Android.
I can get into CWM, but it doesn't see my backup... The backup is in /clockwordmod/backup/2013-03-17-14.09.00 . I can see it when I put my SD card in the PC.
However, CWM isn't finding it when it's in the device, and there's no option to direct CWM to where it is....
Solution anyone?
Click to expand...
Click to collapse
Hi there!
What I can think of is first of all save your CWM backup to your PC.
Then you'd really have to flash a ROM to at least a version that will enable you to use the version of your backup: say if the ROM requirement that you had installed when you made the backup was 4.0.4 then install any ROM of that. You won't have to install any apps then.
You can then install X-parts from Google Play and with that CWM but that will not be a "stuck-on" CWM as any ROM upgrade will remove it BUT the beauty of it is that in your backup [which you'll then copy from your PC to the same folder you describe above make a Restore] you have the CWM that will stick and from there on won't have to worry.
Sounds like a bit of work but personally I don´t see a way around it...this is what I would do to get things as before.
Hope this works for you and do let me know.
Oh and don't forget to click THANKS.
ac3ofS2 said:
Hi there!
What I can think of is first of all save your CWM backup to your PC.
Then you'd really have to flash a ROM to at least a version that will enable you to use the version of your backup: say if the ROM requirement that you had installed when you made the backup was 4.0.4 then install any ROM of that. You won't have to install any apps then.
You can then install X-parts from Google Play and with that CWM but that will not be a "stuck-on" CWM as any ROM upgrade will remove it BUT the beauty of it is that in your backup [which you'll then copy from your PC to the same folder you describe above make a Restore] you have the CWM that will stick and from there on won't have to worry.
Sounds like a bit of work but personally I don´t see a way around it...this is what I would do to get things as before.
Hope this works for you and do let me know.
Oh and don't forget to click THANKS.
Click to expand...
Click to collapse
Yea, what I ended up doing was installing a stock ROM, then installing Rom Manager. From ROM manager the backup installs no problem... But if booting directly to recovery, it can't find it, even though it's in the standard spot... It seems halfway pointless to me to have a backup that can't be restored from recovery... but who am I to judge :silly:
damian5000 said:
Yea, what I ended up doing was installing a stock ROM, then installing Rom Manager. From ROM manager the backup installs no problem... But if booting directly to recovery, it can find it, even though it's in the standard spot... It seems halfway pointless to me to have a backup that can't be restored from recovery... but who am I to judge :silly:
Click to expand...
Click to collapse
Okay... I think I found what the problem was. From within CWM App, I changed storage to external as opposed to internal, now the backups are found from recovery. Not 100% sure that's what the issue was, because I've wiped and installed a couple different ROMs since having the issue.
damian5000 said:
Okay... I think I found what the problem was. From within CWM App, I changed storage to external as opposed to internal, now the backups are found from recovery. Not 100% sure that's what the issue was, because I've wiped and installed a couple different ROMs since having the issue.
Click to expand...
Click to collapse
Hi there mate!
Thanks for sharing what the prob was at the end of it all...I surely learned something and my THANKS to you is given.
See ya around the Forum...
I am a "NOOB" and I completely apologize if this has been discussed previously. My daughter has a Galaxy S3 that someone installed TWRP on it. She tried to update the phone because it gave her the status to do so. Somehow she has wiped everything except TWRP and I have no idea what to do in order to get a OS back on the device. Can someone please help and I really need the information explained to me in the simplest terms. Thanks
In twrp, if you click "restore" does it list anything on either internal or external memory? If so, just restore it and don't update.
Sent from my Slim GS3
dpeeps74 said:
In twrp, if you click "restore" does it list anything on either internal or external memory? If so, just restore it and don't update.
Sent from my Slim GS3
Click to expand...
Click to collapse
It doesn't show anything.
Did you try reboot system?
Odin flash VRBMB1. You'll need a access to Windows for this to work. This will return you to out of the box stock rom.
Do what Slimsnoop suggested. Its for the best
Sent from my SCH-I535 using Tapatalk 4
lol
It just means the SYSTEM was wiped. Just download a small ROM like CM10.1 and flash it. Reboot.
Have had this happen a lot. For a fast fix You will have to load ROM on the external SD card, then when you flash it check the directory where the ROM is stored on the external SD and flash it. Reboot. No need to flash gapps if you don't plan on keeping that ROM.
If you plan on keeping it just download the ROM you want and flash.
SlimSnoopOS said:
Odin flash VRBMB1. You'll need a access to Windows for this to work. This will return you to out of the box stock rom.
Click to expand...
Click to collapse
Ok so this just happened to me and I turned to this awesome site for help. I had switched from CWM to TWRP and installed the img file, when it rebooted into recovery it told me there was no OS installed. I flashed the above referenced file with Odin... when it rebooted though, I had everything I thought I had lost. No stock rom, it was still running cm10 with all my apps and themes, everything.
I'm confused. I'm not a total newbie to this kind of stuff, but I'm by far no expert. I'm just curious if TWRP didn't recogonize anything so it assumed there was no OS installed?
Easy way around this. Happens to me all the time
what you are gonna have to do it download a compatible rom from your computer to a micro sd card. Put the micro sd card in your phone. Go into twrp and select the rom and flash from external sd.