Database Info

How to gain root access to google ion rom?

I'm have the original ION phone with Ion Rom...
But from what i search from wiki to forum's here, mostly I see is reflashing the whole rom to get root access..
is it possible to get the root access on the rom I have now rather than reflashing it?
This is what I have right now in my phone:
HBoot-1.33.3004 (SAPP30000)
CPLD-10
RADIO-2.22.19.261

Yes this is possible.
1. Download a rooted recovery image (recovery.img) with nandroid support.
2. Switch your ion to fastboot mode.
3. Execute "Fastboot boot recovery.img" (this will not flash the recovery to your Ion, it will just load it).
4. perform a nandroid backup.
5. unpack the boot.img you find in the nandroid directory on your sdcard.
6. change the ro.secure property and repack the boot.img.
7. flash the rooted boot.img image to your ion.

So the instruction mention is the same as the one posted on wiki?
http://android-dls.com/wiki/index.php?title=Magic_Rooting
Many thanks!
Mike
Amon_RA said:
Yes this is possible.
1. Download a rooted recovery image (recovery.img) with nandroid support.
2. Switch your ion to fastboot mode.
3. Execute "Fastboot boot recovery.img" (this will not flash the recovery to your Ion, it will just load it).
4. perform a nandroid backup.
5. unpack the boot.img you find in the nandroid directory on your sdcard.
6. change the ro.secure property and repack the boot.img.
7. flash the rooted boot.img image to your ion.
Click to expand...
Click to collapse

No, it's not the same, with the instructions on the wiki your are overwriting your ROM with a different one... so you basically undo the ion rom.

Im very new to this, do you mind bring me throught the how process?
I have just went ahead to try that process..(as i thought its just bascially rooting the magic with the recovery rom and ended up on a boot loop)
Amon_RA said:
No, it's not the same, with the instructions on the wiki your are overwriting your ROM with a different one... so you basically undo the ion rom.
Click to expand...
Click to collapse

5. unpack the boot.img you find in the nandroid directory on your sdcard.
Click to expand...
Click to collapse
How do you do that?

ultraMX said:
How do you do that?
Click to expand...
Click to collapse
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

Thank you Amon_RA!

Hello,
Just got a google ion. Originally followed the instructions in the link above about rooting an htc magic... which allowed me to put haykuro's rootme on. Everything works fine now, I have root (I was able to add new fonts as su). However I do not have a superuser app--- and I am a bit confused about who I receive updates from now. I have read that jf1.5 does not work on this phone.
I did not need to unpack any .img files.
I have a recovery where I can flash new update.zip files, do nandroid backups, etc.
Can anyone fill me in on where I can get a superuser app, who should I receive updated update.zip fles from, etc?
The ion rom that is floating around installs but wifi doesn't work, so I'm back at rootme.zip.

Amon_RA said:
No, it's not the same, with the instructions on the wiki your are overwriting your ROM with a different one... so you basically undo the ion rom.
Click to expand...
Click to collapse
no you don't
I followed the wiki and had ROOT and Hard SPL but the rom was unchanged

When you had root, were you able to install the superuser app or a rom with it?

yochaigal said:
When you had root, were you able to install the superuser app or a rom with it?
Click to expand...
Click to collapse
haven't tried yet
root works fine when plugged into a PC

I have the original Ion as well. The way I rooted my phone was by followed an excellent written tutorial http://www.youtube.com/watch?v=2w_Iyv7wctA (in the upper right hand corner click more details. Then after step step 17 or so continue from the guide on http://android-dls.com/wiki/index.php?title=Magic_Rooting
Great for noobs like me, wouldn'nt have known the commands to put into prompt up to that point and from other guides was not clear if I was supposed to input from phone terminal or prompt on PC but the combination of these two guides helped me get my phone rooted and now I have been trying out the french ROMS 1.8/1.9 and Nok2's V4 full, which is great.

Amon_RA said:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Click to expand...
Click to collapse
Could anyone complete this process succesfully? Can post step by step instructions? the webpage has a lot of information and can be a little confusing...

image - ination
Amon_RA said:
1. Download a rooted recovery image (recovery.img) with nandroid support.
Click to expand...
Click to collapse
Where could I get an image as mentioned here?
Second question: Once rooted, will my phone auto-update the system anymore?
thanks for all the thoughtful answers,
m0j0

mojotexas said:
Where could I get an image as mentioned here?
Click to expand...
Click to collapse
Look at the threads in this same forum...

hankit said:
Im very new to this, do you mind bring me throught the how process?
I have just went ahead to try that process..(as i thought its just bascially rooting the magic with the recovery rom and ended up on a boot loop)
Click to expand...
Click to collapse
I had the same problem and had to restore from nandroid backup... did you solve this issue?

mojotexas said:
Where could I get an image as mentioned here?
Second question: Once rooted, will my phone auto-update the system anymore?
thanks for all the thoughtful answers,
m0j0
Click to expand...
Click to collapse
Mojo, if the root process is done by unpacking and repacking the boot.img you won't alter the original rom so all the features will be untouched.
I've complete the root process on my original ION, if you need any help... post in this threath...

The manual total-geek method on N1?
Yes, I am aware of superboot. downloaded it. Looked at it, and noticed it was an image.
I am one of the weird ones that would rather do this process with the least disruption of the stock bits as possible, or at least know exactly what this image modifies. And while I could be totally blind, I didn't see this listed in my Googling.
I tried the procedure for the ION in this thread and it appears that the Nexus One does something different (maybe an extra checksum check??). Note: I also do have an ION and this procedure worked - so it appears that the procedure is known.
Any further information either about how to modify the appropriate images manually or a description of what the superboot image actually plays with?
Thanks!

I too have a ION and if 2.1 doesn't hit soon I want to root. I am confused. Can someone just post the instructions in order with out having to got a billion links to get the next step.

[SOLVED] Soft Brick... Can't install ROMS and pushing does not work.

First of all I decided to install CM10 without making a backup on TWRP 2 (clever Kyle). Then when it was stuck on the bootanimation for about an hour, I got annoyed and looked through the forums for help. "Factory reset, clear caches before installing etc" So I deleted the ROM, factory reset via TWRP, deleted both cache and then tried to install CM10. Failed.
Then I tried to mount the SD card to my computer to try to find other ROMS to install. Viper and Energy both failed. I then tried CM10, Viper and Energy with CWM 5.8, and the installation of all gets aborted almost instantly, which I am guessing means that it failed on there as well. I then tried ADB, and pushing keeps failing. Does anybody have any ideas at all on how to get just any ROM onto the phone so that I can get the official 4.1 update again (my phone was on 4.1 before trying CM10, so the HBOOT is most likely 4.1 as well). Any advice would be greatly appreciated, because having a £350 paperweight is not what I particularly want, especially considering I have another 9 months contract to run and no spare phone on the same network as my current contract.

kylepont said:
Any advice would be greatly appreciated
Click to expand...
Click to collapse
When you say that installing ROMs fails and adb pushing fails, you should tell us what error messages you get.
If you can still get into bootloader, you're probably going to be fine.
First, check that you can mount your sdcard in recovery. I don't mean mount onto your PC over USB, but just mount the sdcard partition onto the root filesystem.
If you can not get into recovery, re-flash one.
If recovery can not mount the sdcard, then you have to go to the sticky on how to fix unmountable sdcard. It involves flashing a stock recovery and then clearing storage from bootloader.
If your recovery is good and your sdcard is mountable, adb pushing should work. If it doesn't, post error messages. Make sure your sdcard is mounted before you try to push fils to it.
In recovery, format system, data, cache, but not sdcard. Then flash a zip. Then boot back into bootloader/fastboot and fastboot flash the boot image that comes with the rom. (Did you do this last step when flashing other roms?)
If this does not work not for you, describe in detail what you do and what you see. If it does work out, I suggest you make a nandroid backup so you can get back to this state, and S-off the device.
-Jobo

touch of jobo said:
If this does not work not for you, describe in detail what you do and what you see.
Click to expand...
Click to collapse
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update

Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update
Click to expand...
Click to collapse
Have you flashed the boot.img?
fastboot flash boot boot.img
Sent from my One S using Tapatalk 2

usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img
Click to expand...
Click to collapse
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?

kylepont said:
Sometimes a print screen can speak louder than words.
Click to expand...
Click to collapse
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Edit:
kylepont said:
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
The flashing instructions for your ROM will likely state that you have to 'flash the boot image (or boot.img or kernel) in fastboot before booting into the rom.
You can find a file named 'boot.img' inside your rom zip. You have to flash that in fastboot. You can do it before or after flashing the rom, but you must do it before booting into the rom.

kylepont said:
usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img/QUOTE]
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
Extract the boot.img file from the ROM. Place it in your adb folder. Boot into bootloader, select fastboot and connect to PC. Type command fastboot flash boot boot img
Click to expand...
Click to collapse

touch of jobo said:
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Click to expand...
Click to collapse
All the boxes are ticked on the TWRP Mount screen, including System and SD card. And yes, I did make sure that it is:
1) in the same folder as the adb
2) called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
And usaff22, does that involve unzipping the ROM that I am using?

Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...

kylepont said:
I did make sure that it is [...] called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
Click to expand...
Click to collapse
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
kylepont said:
Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...
Click to expand...
Click to collapse
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Also, does it say anything interesting when it fails?
Before flashing the zip, did you format your system, data, cache partitions?

EDIT: After repeatedly trying to adb push, I finally got CM10.zip.zip onto the phone. Flashing took a bit longer than last time, but booting took no time at all. Thank you touch of jobo and usaff22, your advice was a lot of help.
touch of jobo said:
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
Click to expand...
Click to collapse
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
touch of jobo said:
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Click to expand...
Click to collapse
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
touch of jobo said:
Before flashing the zip, did you format your system, data, cache partitions?
Click to expand...
Click to collapse
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder

kylepont said:
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
Click to expand...
Click to collapse
I can't help with that adb error. Never seen it. Try searching the forums for it. Sorry. Also, I don't use Windows, so I don't know about driver versions and things.
kylepont said:
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
Click to expand...
Click to collapse
TWRP and CWM are both fine for flashing ROMs, just not this specific version of TWRP. Since I dont use it myself, I dont know the exact version numbers, but read around a bit and you'll find what worked for others.
Maybe flashing a different recovery will even get rid of your protocol error.
If you've made nandroid backups (I guess you havent or we wouldnt be here.. sorry) you should stay with the same recovery (same 'brand', not same version) or you can't restore them.
kylepont said:
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder
Click to expand...
Click to collapse
The CM10.zip should be on your sdcard, not your system partition. You dont need the boot img at all on your device. You need it on your PC in order to fastboot flash it.
Before flashing a ROM you should wipe your 'system', 'data', and 'cache' partitions, but not your 'sdcard' partition. Only if you flash (a newer version of) the same ROM you have operational, then you can sometimes flash without wiping. This is called 'dirty flashing'. But this does not apply in your case.

Successful flash of CyanogenMod, thanks for the help.
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.

Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.
Click to expand...
Click to collapse
I would rename the zip to something else like sense.zip, place it on the desktop and do adb push C:\Users\username\Desktop\sense.zip /sdcard/
Make sure you use backward slashes for the PC file location, and forward slashes for the phone paste location.
This way we are also providing the full path on the PC.
Also make sure you use the latest adb from the SDK website. You don't need the whole thing, just the platform-tools bit, and replace the files in the new folder with the old one.
Sent from my One S using Tapatalk 2

Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.

kylepont said:
Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.
Click to expand...
Click to collapse
You might be able to find an RUU lying around on one of the websites which give RUUs such as androidfiles.org/ruu
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.

kylepont said:
the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required)
Click to expand...
Click to collapse
You can extract the recovery image from any RUU or OTA. Recoveries do not depend on carrier.
But .. if you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.

touch of jobo said:
If you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.
Click to expand...
Click to collapse
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
usaff22 said:
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.
Click to expand...
Click to collapse
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.

kylepont said:
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
Click to expand...
Click to collapse
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
kylepont said:
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.
Click to expand...
Click to collapse
This is the thread: http://forum.xda-developers.com/showthread.php?t=1671643
It involves extracting, hex-editing, and flashing a critical part of your device. If you make the slightest mistake you have a brick. However, if you read carefully and double check every step, it's not difficult. Many have done it. Read the thread.
Once you have supercid, you may as well get s-off as well. (This is the thread: http://forum.xda-developers.com/showthread.php?t=2155135 ) That way you can always flash anything.
Whatever you decide to do, before you start on anything, read all the instructions to the end, so that you're sure you can complete the process before you start. Also, before you start any process, try to understand what each step does and why it is necessary. That may involve a lot of reading and searching, but that is a Good Thing in the end.

touch of jobo said:
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
Click to expand...
Click to collapse
It is unmountable. I tried CWM and TWRP to no avail. Also, I have HBOOT version 2.15 which I heard is a bugger to work with. Also, I got the ZIP file for the stock 4.1, and I read that the stock recovery is in the firmware folder, but I cannot access it. (https://www.dropbox.com/s/kyn9sb5x7gpd7fr/Picture2.png) Then, I tried to get to the CID, following the instructions that you gave me, and I didn't get very far (https://www.dropbox.com/s/g6ik0i3los7unde/Picture3.png)

how to update to 4.4.x after this... New to android

First of all, I have been reading this forum for about two weeks and just registered in order to get some help as I do not want to break my one week old nexus 5.
From my reading, the updates can be done in quite different ways and because of that I want to be sure what I should do.
I started by:
- root the mobile with cf-auto root. It did everything for me, got the superuser icon automatically
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
- other than that, I have installed some root only apps like rom manager, greenify, root Explorer, etc. I supported those developers with purchase. Those guys deserve it.
Anyway, i am looking for the safe way to update to 4.4.1. I read some members saying they lost root after the update, others lost something else (I am referring to the thread on nexus 5 general forum).
Can you help me? What path shall I go? Thanks a lot.

To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.

cesar.maranhao said:
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
Click to expand...
Click to collapse
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers

shotta35 said:
To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.
Click to expand...
Click to collapse
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)

finistere said:
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers
Click to expand...
Click to collapse
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?

cesar.maranhao said:
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)
Click to expand...
Click to collapse
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
cesar.maranhao said:
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?
Click to expand...
Click to collapse
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.

shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!

cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076

shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
shotta35 said:
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076
Click to expand...
Click to collapse
yes, i have been reading those topics and many others.. i managed to solve the adb device unauthorized anyway. just flashed the 4.4.1 zip file under clockwork mod recover.. android is upgrading at the moment. lets see if everything is work as it should.

No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.

RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM.. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.

cesar.maranhao said:
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.
Click to expand...
Click to collapse
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..

RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?

cesar.maranhao said:
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?
Click to expand...
Click to collapse
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.

RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost

cesar.maranhao said:
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost
Click to expand...
Click to collapse
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905

RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
RusherDude said:
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!

cesar.maranhao said:
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!
Click to expand...
Click to collapse
done it! i now have root again and the clockworkmod custom recovery! nice!
:good:

RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
from where can i get the flashable clokwork mod recovery zip file?
i am going to apply the 4.4.2 update now and will be doing it this way:
from the recovery apply the 4.4.2 zip. after this apply the supersu zip. i want to install the custom recovery zip too so when the phone restarts everything will be configured. is this possible?

RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
well, it seems i haven't lost my custom recovery. was it because i installed the supersu before rebooting?

I want to restore my Blu phone to the stock version.

So, I ended up soft bricking my device in some way(??) I factory reseted the phone and it loads, i even set up my wifi, but when Im going to put my gmail account it crashes. I just want to restore it to its original settings. I have no backups, I feel screwed, Im literally in tears because this was a gift from my mother. Please Help me. :crying:

Go to page 23 of the blue development thread. The stock .img are there.

How do I use the stock.img to fix my phone?
Does it work as a backup if I place it in my phone?

futuresenseidomo said:
How do I use the stock.img to fix my phone?
Does it work as a backup if I place it in my phone?
Click to expand...
Click to collapse
You need a Windows program called SP Flash Tool and a scatter file for the Pure XL which is also in the development thread. Load the scatter file, select the partitions you want to restore (generally recovery, boot, and system) and load the .IMG files for them (should be recovery.img, boot.img, system.img or something close.)

Or another way to do it, if you have Twrp installed is to add to boot.img and recovery.img along with Meta-inf folder and zip it up. Then flash it in twrp. It will return your device to stock.

futuresenseidomo said:
How do I use the stock.img to fix my phone?
Does it work as a backup if I place it in my phone?
Click to expand...
Click to collapse
Were you able to get it working again? Having a very similar issue.

So now what can I upgrade my Stock ROM to?

Hello, I'm a noob at this so please be kind. I followed the below:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
I successfully:
Unlocked my TF300T's Bootloader
Installed custom recovery using fastboot
Rooted my tablet
Debloated the Tablet (Titanium Backup)
Backup up my current (OEM) SYSTEM ROM to microSD
So now I'm onto attempting a custom ROM. I'm a bit bored with 4.2.1 and would like to go to the same version of ROM my Note 7 has which is 6.0.1 Marshmallow or even try the new 7.0 Nougat.
I'm a little confused as to what ROM will or will not work. I see a few ROMS worth trying, but there install instructions reference a different Bootloader multiple flashes such as SuperSU or gapps.
Whats the best fool proof method to flash a new ROM with what I have and are there any simple one file ROM/ZIP/ Blob etc.. file that would do what I want?
Thank you.

broderp said:
Hello, I'm a noob at this so please be kind. I followed the below:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
I successfully:
Unlocked my TF300T's Bootloader
Installed custom recovery using fastboot
Rooted my tablet
Debloated the Tablet (Titanium Backup)
Backup up my current (OEM) SYSTEM ROM to microSD
So now I'm onto attempting a custom ROM. I'm a bit bored with 4.2.1 and would like to go to the same version of ROM my Note 7 has which is 6.0.1 Marshmallow or even try the new 7.0 Nougat.
I'm a little confused as to what ROM will or will not work. I see a few ROMS worth trying, but there install instructions reference a different Bootloader multiple flashes such as SuperSU or gapps.
Whats the best fool proof method to flash a new ROM with what I have and are there any simple one file ROM/ZIP/ Blob etc.. file that would do what I want?
Thank you.
Click to expand...
Click to collapse
Congratulations! Everything you did looks fine. So you are ready to install a custom rom. I would like to suggest one of the best: http://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 (You may follow up the tread and report there!)
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!

ebonit said:
Congratulations! Everything you did looks fine. So you are ready to install a custom rom. I would like to suggest one of the best: http://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 (You may follow up the tread and report there!)
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
Click to expand...
Click to collapse
Thanks. As simple as the process was, as a noob (first time attempting this) I was really concerned about screwing this up and bricking my tablet.
The one you linked to was one of the ones I was considering and hence my question regarding what works with what I have already done. The noob mind (mine anyways) finds a dozen questions at every turn. In this case I would ask the following:
Q-Do I have to use Kang TWRP?
Q-How is it different than the TWRP I used on my Tablet?
Q-Will I need to constantly change TWRP versions depending on what ROM I want to use?
Q-Is there a danger to switching TWRPs?
Q-Doesn't flashing SuperSU after I flash Gapps overright and erase SuperSU or is there some unique way to flash (push?) both at the same time?
Q-Many more I'm sure!
To the noob, almost all the instructions I read appear to be written for someone who as done this many times. The level of detail needed for the novice is just not there or lost between the jargon used, with many steps not fleshed out because the author assumes a certain level of expertise.
I will definitely read these threads as best I can, but in the interim, is there any ROM that are known to be able to be flashed via the TWRP I currently have? The author of the version I used certainly made it seem like it was that simple, load the ROM/ zip file onto the MicroSD card and when in Custom recovery simply use the INSTALL feature to navigate to the file and press a button to flash and ..."BAM!!" you are running a new ROM.

ebonit said:
...
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
Click to expand...
Click to collapse
That version of KANG appears to be dead, as the thread has been closed and abondoned by the OP. So no new questions or help there....
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)

broderp said:
That version of KANG appears to be dead, as the thread has been closed and abondoned by the OP. So no new questions or help there....
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
Click to expand...
Click to collapse
Please don't brick your tablet. First download Kang TWRP. It isn't dead. Try this https://www.androidfilehost.com/?fid=24052804347781183.

broderp said:
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
Click to expand...
Click to collapse
Yes you can.
However Kang TWRP is a xxx.img file. You also can use your current TWRP and flash the image file. Attached you will find an image and a zip version.

ebonit said:
Please don't brick your tablet. First download Kang TWRP. It isn't dead. Try this https://www.androidfilehost.com/?fid=24052804347781183.
Click to expand...
Click to collapse
Sorry, bad choice of words on my part. By dead I meant that the thread was closed and I'm concerned getting answers would be harder as the OP was no longer actively looking there for questions.
ebonit said:
Yes you can.
However Kang TWRP is a xxx.img file. You also can use your current TWRP and flash the image file. Attached you will find an image and a zip version.
Click to expand...
Click to collapse
Ok, so if I read your comment correctly, I can copy the .img file to an SD card, boot into recovery and flash it from there OR I can fire up fastboot and the same steps I originally did to install custom recovery from my PC to accomplish the same thing... either way I should still have custom recovery, but with the KANG version. Right?
THANKS TO BOTH OF YOU FOR RESPONDING TO MY PREVIOUS POST. I appreciate the support.

Oh no....
Well crap. I put the .img file on my SD card and boot the tablet into recovery, I flashed the .img file to the rovery not boot partition. All appeared well....but when I go back to see if I have KANG recovery, it hangs anbd says Booting Failure Unrecoverable bootloader error (0x000000000)
EDIT: After I cleaned my pants, I used abd and fastboot to flash the original Blob file using my PC. This restored the custom recovery. I was freaking out for a few minutes.
I didn't change the file name of the kang .img file. Should I have done something different?
EDIT: Successful recovery to Kang2.8.7.2 !! :good::good: I used adb and my PC to send the .img file (renamed "twrpkang.img" for simplicity) and it worked great. I'm a pro..:silly:

broderp said:
Well crap. I put the .img file on my SD card and boot the tablet into recovery, I flashed the .img file to the rovery not boot partition. All appeared well....but when I go back to see if I have KANG recovery, it hangs anbd says Booting Failure Unrecoverable bootloader error (0x000000000)
Click to expand...
Click to collapse
Bad luck! Could you please describe what does it mean? : "I flashed the .img file to the rovery not boot partition."

ebonit said:
Bad luck! Could you please describe what does it mean? : "I flashed the .img file to the rovery not boot partition."
Click to expand...
Click to collapse
Not sure what I did wrong. I tried to do it within the old recovery menu and it hosed it. It found the file and mounted it successfully, but it seemed weird to be within the partition I was overwriting and writing to it. Kind of like you cant install windows while your using Windows...
The new version is much smoother.... Thanks, not to learn about this gapps super SU and how to flash all of these and in what order along with the ROM..as well as this wipe vs format thing...so confusing...