Hello people
I think my HTC Hero is what you call softbricked.
When I hold Home + Power on to go to recovery mode I get this single line of text:
Build : RA-hero-v1.5.2
If I hold Home and press power on the text disappears leaving an all black screen. Pressing home + power on again brings the text back.
When I boot normally it just keeps saying "Hero"
I think I did a full wipe, installed VillainROM 6.0.0 and then did a OTA update to VillainROM 6.1.0. I did notice the latest rom being rather slow and hanging sometimes. Then three days ago it froze. I pulled the battery and when I put it back in I was left with what I've described above.
Can't access VillainROM's official website
Another frustrating thing is that w w w. villainrom .co .uk has seemed down to me this whole softbrick-period. But they've announced a new version and no one have commented on their site being down. Apparently I'm the only one who can't access it.
Vol. down + power on
I've never used this boot mode. But it's the only one which seems to work.
HBOOT says Sd checking and all the tests results in:
No image! or No image or wrong image!
FASTBOOT just gives a red box with the white text FASTBOOT in it.
What can i do?
I did a nandroid backup before installing VillainROM 6.0.0 but I can't access recovery mode.
I would like to install the official 1.5 RUU-rom but HTC Sync can't find my phone, neither can adb shell.
I can insert the SD card in my computer and put an update.zip file in the root. Is this a solution? I don't know how to make the phone boot the update.zip file or how this works.
Sorry for this long post. I've been searching the web ever since thursday without any luck. So now I'm just putting all I've experienced out.
I hope someone can help me. I would be very glad
Alright, if you can get to the fastboot screen, this is what you should do:
Plug your hero in fastboot mode into a computer with the latest android sdk installed.
DL the latest recovery for your device: I don't think I can post links yet so search the forum for Amon RA's recovery (1.6.2) and place it in the tools folder of the sdk.
Then:
Open a command prompt (or terminal for linux, idk for mac)
Go to the tools folder with cd
(./)fastboot boot recovery-RA-hero-v1.6.2.img
(./ is for linux ^^,) And that should normally work
From there your best bet is to use Nandroid to recover one of your backups.
Thank you for your response
But I got an error:
Code:
C:\android-sdk-windows\tools\fastboot boot recovery-RA-hero-v1.6.2.img
downloading 'boot.img' ... FAILED (remote: not allow)
finished. total time: 0.010s
The site I downloaded the recovery image from suggestion this installation:
via fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader fastboot boot recovery-RA-hero-v1.6.2.img adb shell mount /sdcard adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img adb shell reboot
I've also tried this but it resulted in: error: device not found
I've noticed how my phone says "fastboot usb" when connected to my computer.
Re: Hangs on boot to recovery mode and normal mode
NessGuard said:
Thank you for your response
But I got an error:
Code:
C:\android-sdk-windows\tools\fastboot boot recovery-RA-hero-v1.6.2.img
downloading 'boot.img' ... FAILED (remote: not allow)
finished. total time: 0.010s
The site I downloaded the recovery image from suggestion this installation:
via fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader fastboot boot recovery-RA-hero-v1.6.2.img adb shell mount /sdcard adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img adb shell reboot
I've also tried this but it resulted in: error: device not found
I've noticed how my phone says "fastboot usb" when connected to my computer.
Click to expand...
Click to collapse
Have you flashed the official 2.1 rom thats been floating round?
Sent from my HTC Hero using Tapatalk
AndroHero said:
Have you flashed the official 2.1 rom thats been floating round?
Click to expand...
Click to collapse
No, I haven't.
Just now I did this:
Code:
C:\android-sdk-windows\tools\adb devices
List of devices attached
And none was shown...
Then I did:
Code:
C:\android-sdk-windows\tools\fastboot devices
HT97TL903447 fastboot
Is this some sort of serial number of my phone?
Re: Hangs on boot to recovery mode and normal mode
Your sd card is seen by your phone or not ?
sebxd said:
Your sd card is seen by your phone or not ?
Click to expand...
Click to collapse
How can I check this?
Hboot says Sd checking and all the tests results in:
Code:
No image! [I]or[/I] No image or wrong image!
The site isn't down, but some people can't get to it due to their DNS setup.
Use 8.8.8.8 and 8.8.4.4 to get it, or go to http://villainrom.grense.no/villainrom.co.uk to get in.
Re: Hangs on boot to recovery mode and normal mode
Mmm if i'm right you can't boot normaly ? It's strange..
Have you tried to boot without your sd card ?
I don't really know what the answer of fastboot means..
anon2122 said:
The site isn't down, but some people can't get to it due to their DNS setup.
Use 8.8.8.8 and 8.8.4.4 to get it, or go to
[url not allowed] to get in.
Click to expand...
Click to collapse
Thanks, but I think I will just stick to this forum. Hope I can get a solution
sebxd said:
Mmm if i'm right you can't boot normaly ? It's strange..
Have you tried to boot without your sd card ?
I don't really know what the answer of fastboot means..
Click to expand...
Click to collapse
Yes, I have tried booting without SD card and without simcard aswell. My simcard is now in a good old Nokia 3310
I have updated the radio earlier
A while ago I updated the radio to this version: 63.18.55.06JU_6.35.09.26
Is that an android 2.1-radio? And is that what's causing "not allow" when running fastboot flash?
What recovery image would I then be allowed to flash? An official one?
Or is it my bootloader (that's SPL, right?) that needs to be flashed to a version that allows the fastboot flashing?
I haven't been able to find a guide on flashing SPL on HTC Hero.
Is this the way to go?
Still need help or is this now sorted?....
It's now working
My phone is now working. I did the following:
1. Connected my phone to a computer with HTC Sync and drivers installed.
2. Started the bootloader on my phone (vol. down + power on, hold until bootloader starts).
3. Pressed back to start fastboot. It said fastboot usb because it was connected to my computer.
4. I tried to install an official 1.5 RUU rom. The phone responded and began the process. It cleared/deleted some caches/files or something. But then my computer and my phone said that the ROM installation had failed and that I should find the right rom.
5. Somehow this cleaned up the phone so I now could boot in recovery mode as I used to (I didn't try a normal boot, so can't say if that worked). I did a full wipe and flashed a custom rom (not VillainROM 6.0.0 ).
Even though VillainROM has made me sad I will now go for VillainROM 10.
Wish me luck
And thanks for your responses.
Brilliant. Just edit the title of your thread to put [SOLVED] on.
And good luck, but i'm sure you wont need it.
EDIT...... Excellent, done it already.
ddotpatel said:
EDIT...... Excellent, done it already.
Click to expand...
Click to collapse
Hehe, yes, even though it's my first post I am a little bit smart
Oh nice ! You have done it ! It is really smart indeed and I'm happy for you !
its not solved for my hero
i tried everything within last two days. but i havent succeess. (i tried your solition too)
i did nondroid backup and then restore. finaly my phone doesnt open.
and after i have given the same your errors (from adb and phone)...
but i havent success..
where i do wrong?
thanks...
Can you explain what you did, what are the errors and when does it appears please
EDIT...... Excellent, done it already.
Click to expand...
Click to collapse
Hehe, yes, even though it's my first post I am a little bit smart
Click to expand...
Click to collapse
Indeed. I'm sorry, I never meant to sound like an ass.
-------------------------------------
Sent via the XDA Tapatalk App
Related
After trying to install ICS on my folio 100 using Rom manager, the update to ICS failed. Now the Folio 100 starts normally, but it doesn’t react on the buttons (power + vol +, 3x power vol 1). It just starts normally and after that I can use everything the normal way. Except when I change language from English into Nederlands, it’s not saved and after a restart of the system it’s back in English again, including the time zone which will be back to GMT +00.00 which is very annoying. The only way to get rid of this is to reinstall Android 3. By the way, factory reset doesn’t reset anything. It just restarts the Folio.
Getting into recovery from the menu or from Rom manager won’t do the trick either. The only thing I can use is ABD. But the command “flash_image recovery recovery.img” gives an error: “Error scanning partitions: No such file or directory”. And the file is in the system-directory. So this is a dead end for me too. I searched the forum and the internet, tried several possibilities, but now I’m stuck. I’ve considered opening the Folio and to start it without NAND connected, but I haven’t tried this, because I still hope for a software solution. What will happen when I manually delete of format the internal SD? Is there anyone who can help me to get my folio into recovery one way or another? Data is lost already, so that’s no problem anymore in this case.
Fastboot command is: fastboot flash recovery recovery.x.y.z.img ... not flash_image recovery.img (name of the recovery ofc)
Ics ? CM9? If so just read the tutorial on the topic related its simple as hell...
Also best way to start an new: fast boot erase Linux/recovery/system/cache/userdata one after another then fastboot reboot (remove USB before it reboot) check the folio say magic mismatch error then reboot pressing long on power(6sec) then the recovery command.
Sent from my folio100 using XDA Premium HD app
Thanks but...
ReiverBlade said:
Fastboot command is: fastboot flash recovery recovery.x.y.z.img ... not flash_image recovery.img (name of the recovery ofc)
Ics ? CM9? If so just read the tutorial on the topic related its simple as hell...
Also best way to start an new: fast boot erase Linux/recovery/system/cache/userdata one after another then fastboot reboot (remove USB before it reboot) check the folio say magic mismatch error then reboot pressing long on power(6sec) then the recovery command.
Sent from my folio100 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, but this isn't the solution. The main problem is that I can't get my Folio into fastboot/recovery mode anymore. After that updating is simple. Done it several times before. Do you have a suggestion how I can get it into fastboot/recovery mode. ADB wont work either.
Regards Erik
Weird... hum im not home but i will check that( full keyboard is easier to answer xD)
Sent from my GT-I9000 using XDA
ErikSnippe said:
Thanks, but this isn't the solution. The main problem is that I can't get my Folio into fastboot/recovery mode anymore. After that updating is simple. Done it several times before. Do you have a suggestion how I can get it into fastboot/recovery mode. ADB wont work either.
Regards Erik
Click to expand...
Click to collapse
Remove the sdcard!
Remove SD Card
stefannsv said:
Remove the sdcard!
Click to expand...
Click to collapse
I removed the external SD-card (to the right of the orange light). But that doesn't help. How can I remove the internal SD-card? I removed the back and the battery but I do not find a sd-card. Unmounting the internal SD-card doesn't do the trick either.
did You come in the recovery menu??
I think you flashed the ics withe the wrong recovery...
flash the old rom aigan (copy the update.zip in the sdcard and update the folio via recovery menu)
when that works, try aigan with fastboot to flash first boot, then recovery (but the right version!!)
stefannsv said:
did You come in the recovery menu??
I think you flashed the ics withe the wrong recovery...
flash the old rom aigan (copy the update.zip in the sdcard and update the folio via recovery menu)
when that works, try aigan with fastboot to flash first boot, then recovery (but the right version!!)
Click to expand...
Click to collapse
I think you're absolutely rigth about flashing the wrong recovery. Problem is that I can't come into a recovery menu (power + vol up). Fastboot won't work either (3xpower + vol up). I've used both before, so the configuration on my pc is right. Now al I have to do is boot into recovery or into fastboot. That's my problem, flashing with the working Honeycomb-version is no problem at al when I get into the recovery menu. Do you no what happens if I delete the complete /system/-directory on my folio? Is that an option to force the tab into recovery?
...and how want you delete the complete sys? do you mean with root explorer in rw-option?? thats very dangerous...can't you flash with rom manager?
Rom Manager
stefannsv said:
...and how want you delete the complete sys? do you mean with root explorer in rw-option?? thats very dangerous...can't you flash with rom manager?
Click to expand...
Click to collapse
I can access the internal sd-card using ADB. This way I should be able to delete/move/copy files. After puting the system-partionion in RW-state. In Adb shell the command "flash_image recover recover.img" gives an error "erros scanning partitions: No such file or directory". The image files exists! So I'm stuck there too.
I tried to use rommanager. It work once when i was installing ICS. After this it won't boot into recovery. When I use "Flash clockworkmod recovery" in Rommanager v5.0.0.6 i only get the following phone models: Advent Vega, Elocity A7, LG/T-mobile G2X, LGE Optimus 2x, Motorolo XOOM and Viewsonic Gtablet (smb_a1002) - bootloader 1.1. I tried all the phone models, but all they do is reboot the tablet. No choice will boot into recovery. Also tried clockworkmod recovery 2.5.1.4 but also no succes.
I do not know how to install clockworkmod 3.0.0.5 for Folio. I only can find an option to install it using recovery menu or fastboot. And both won't work on my tablet.
and you have put the recover.img file in the fastboot directory?
stefannsv said:
and you have put the recover.img file in the fastboot directory?
Click to expand...
Click to collapse
Where can i find the fastboot directory?
Here I've ad complain the Problem:
http://forum.xda-developers.com/showpost.php?p=23715985&postcount=467
the fastbootdirectory is in android-sdk-windows\platform-tools
There is the fastboot.exe too.
Put the two files in that directory, connect yout folio via usb in fastboot modus with your pc or laptop, make the described commands at windows shell.
stefannsv said:
Here I've ad complain the Problem:
http://forum.xda-developers.com/showpost.php?p=23715985&postcount=467
the fastbootdirectory is in android-sdk-windows\platform-tools
There is the fastboot.exe too.
Put the two files in that directory, connect yout folio via usb in fastboot modus with your pc or laptop, make the described commands at windows shell.
Click to expand...
Click to collapse
Still the main problem is that I can't put my folio into fastbootmode via usb.
so far only 2 things prevent my folio to go into fastboot: power cord and/or mini usb unplugged.
also you talk about removing internal SD but you know what they reffere as internal SD is : a chip soldered on the motherboard?Right?
one more thing lets make it clear: fasboot directory isnt fixed, for the sake of accessibility you can put it like me C:\tools_X
also renaming recovery5.0.0.4.img (the one from nopy) into recoveryA.img (i wonder if your error come because you write the wrong commande or if its because of recover.img instead of the right name for the file.)
last option before saying: you F***ed up your tablet if nothing mentioned above works
also side note: every answer from you after a recommendation from a user : contain a new error \\\ important your problem come from : not being able to go into fastboot mode or not being able to flash the recovery via fastboot (either due to : you putting the recovery img not in the right directory or input the wrong command) its important since 1st one is prolly f.u.b.a.r and the second one is recoverable by reading and doing step by step whats explain *exactely what is explain*
the only right command is : "fastboot flash recovery *name of the recovery*.img" and not Flash_recover recover.img as you write it 2 time now
Sent from my folio100 using XDA Premium HD app
ReiverBlade said:
so far only 2 things prevent my folio to go into fastboot: power cord and/or mini usb unplugged.
also you talk about removing internal SD but you know what they reffere as internal SD is : a chip soldered on the motherboard?Right?
one more thing lets make it clear: fasboot directory isnt fixed, for the sake of accessibility you can put it like me C:\tools_X
also renaming recovery5.0.0.4.img (the one from nopy) into recoveryA.img (i wonder if your error come because you write the wrong commande or if its because of recover.img instead of the right name for the file.)
last option before saying: you F***ed up your tablet if nothing mentioned above works
also side note: every answer from you after a recommendation from a user : contain a new error \\\ important your problem come from : not being able to go into fastboot mode or not being able to flash the recovery via fastboot (either due to : you putting the recovery img not in the right directory or input the wrong command) its important since 1st one is prolly f.u.b.a.r and the second one is recoverable by reading and doing step by step whats explain *exactely what is explain*
the only right command is : "fastboot flash recovery *name of the recovery*.img" and not Flash_recover recover.img as you write it 2 time now
Sent from my folio100 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for your help,
the fastboot command fastboot flash recovery......... doesn't work. My pc keeps waiting for the device. Which is to be expected while i can't boot my folio into fastboot-mode. The command i used before is in adb shell.
Can you tell me where to put recovery.img exactly on my folio? And what i should do after i,ve put it there. I can use a root-explorer on my folio and i can use adb push ...... to move or copy files. Also mounting system in rw-mode is no problem anymore. My folio is rooted and i can use it as root or su in adb-shell.
ErikSnippe said:
Thanks for your help,
the fastboot command fastboot flash recovery......... doesn't work. My pc keeps waiting for the device. Which is to be expected while i can't boot my folio into fastboot-mode. The command i used before is in adb shell.
Can you tell me where to put recovery.img exactly on my folio? And what i should do after i,ve put it there. I can use a root-explorer on my folio and i can use adb push ...... to move or copy files. Also mounting system in rw-mode is no problem anymore. My folio is rooted and i can use it as root or su in adb-shell.
Click to expand...
Click to collapse
Don't put the recovery.img into the folio! Copy it to your pc. In the folder where the fastboot.exe is. Then start your folio an go in the fastboot modus (power and three times volume up)
Connect your folio via mini-usb with your pc and open a windows shell(cmd).
Now type
fastboot erase recovery
Fastboot flash recovery nameoftherecoveryfile
stefannsv said:
Don't put the recovery.img into the folio! Copy it to your pc. In the folder where the fastboot.exe is. Then start your folio an go in the fastboot modus (power and three times volume up)
Connect your folio via mini-usb with your pc and open a windows shell(cmd).
Now type
fastboot erase recovery
Fastboot flash recovery nameoftherecoveryfile
Click to expand...
Click to collapse
I can't get into fastboot-mode with my folio!!!!!!! That's the whole problem. The pc stays waiting for the device!
ErikSnippe said:
I can't get into fastboot-mode with my folio!!!!!!! That's the whole problem. The pc stays waiting for the device!
Click to expand...
Click to collapse
install PDANet on your pc
ErikSnippe said:
I can't get into fastboot-mode with my folio!!!!!!! That's the whole problem. The pc stays waiting for the device!
Click to expand...
Click to collapse
Is the problem the fastboot modus at the folio or the connection to your pc?
Flashed the Broccoli nightly rom I can no longer boot or get back into CWM. Computer cannot start the device. Can someone please help me? Tried all the tools and methods. It won't work unless I can get the device to start when connected to my computer.
RIght now when I press Vol Up and power, it brings me to cold boot linux. Cannot select anything or do anything. When connected to comp, it says device cannot start Code 10. Don't know what else to do. Help please
Looks like you're having an issue similar to mine. You'll need to setup ADB and push another rom to your Prime.
Can you get into recovery?
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
This thing is completely frozen no matter what. I can power off and on but that's about it. The device won't start according to windows. I'm praying I won't have to RMA or something.
You shouldn't be getting that screen pressing vol up and power.....that should be vol down and power, then doing nothing.
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
Thats pretty strange. You kinda screwed unless you can get into recovery or fastboot
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
Hi,
where it says press down to change mode you should be able to highlight the middle icon. If so that is fastboot and you have a chance.
I had a very bricked Prime and it only got that far. Then I followed this post.
You must download the fastboot and adb from the links given. I had some from elsewhere and they didn't work so well.
Also, I am not an Android hacker and I think that the dd command is somehow dangerous. At the end of the day, on my machine, I'm back with AndroWook and latest Motley kernel
Best of luck.
Tritium
Thanks let me try now. I hope it works. How did you get the computer to recognize the prime? Do I need to enable asus sync?
Tritium3.016 said:
Hi,
where it says press down to change mode you should be able to highlight the middle icon. If so that is fastboot and you have a chance.
I had a very bricked Prime and it only got that far. Then I followed this post.
You must download the fastboot and adb from the links given. I had some from elsewhere and they didn't work so well.
Also, I am not an Android hacker and I think that the dd command is somehow dangerous. At the end of the day, on my machine, I'm back with AndroWook and latest Motley kernel
Best of luck.
Tritium
Click to expand...
Click to collapse
It's alive!!! Thanks for the help. :good:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
klutch said:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
Click to expand...
Click to collapse
So when your device turns on its in a recovery loop right? You try to reboot and it goes right back to recovery?
It's ok don't worry, we will get it fixed. If that's what your problem is its referred to brick 1a in the unbrick your prime sticky thread.
We just need to setup ADB if you haven't already, and run one command. PM me if you need some help and ill try my best to get you through it or remotely connect to your computer to help you.
I highly suggest TWRP recovery after you get rebooted.
Sent from my ADR6425LVW using xda premium
klutch said:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
Click to expand...
Click to collapse
This is what I did while in CWM. Below is a copy of an insert from this thread.
http://forum.xda-developers.com/showthread.php?p=24923189#post24923189
Anyhow, so after you have that version installed:
1. Download "ROOTED 9.4.2.21 CWM compatible signed US version"
d - h . s t / r 4 4 -> WITH NO SPACE! (This is from the Primeval: The STOCK stock rom) Thread.
2. EXTRACT IT to the same directory where your ADB is! We only need the BLOBFILE from that zip folder!
3. Once you have the files extracted just run the following on your Command line:
adb push blobfile /sdcard/ ---> Its going to look like its not doing
nothing but dont worry its doing it in the background after 401 or some
seconds the command line will returned to you with a message like this:
1275kb, dadadada...
4. VERY IMPORTANT!: enter:
adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4
(Same as the previews step it will take forever but it will work dude!)
5. DONE! at least this is what worked for me man!
Im so happy now my Asus is freaking Brand NEw again! i was JUST about to through this garbage away but im so happy "dklue" gave me the BLOB concept idea! heheheh i guess i learned something new now..
the thing is the computer is not picking it up i tried diffrent drivers and still nothing i try doing ADB Shell device not found in order to do some commands i have to have it mount and thats the problem what ever i do wont move nothing so basicly is still on CWM only reboot and back again to CWM
Hold power and vol down to boot into CWM. Then you can do the blobfile push. It worked for me
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
perch_44 said:
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
Click to expand...
Click to collapse
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
flumpster said:
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
Click to expand...
Click to collapse
If that fails, I had the same issue with cwm, I installed twrp via fastboot and haven't had the problem of the file not showing up after adb push. Fustrating I know.... I tired everything I could think of in cwm multiple reboots different usb ports... on an on......
Please HELP CWM Roocovery Loop!!!
perch_44 said:
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
Click to expand...
Click to collapse
I am having the same exact problem. It started when I tried to restore my stock backup that I made using CWM 5.8.2.0 coming from the CM rom. I am stuck in the CWM recovery screen and cant get ADB to see the TF Prime. I just get error: device not found. How did you manage to push a zip if ADB wasn't seeing your device? I have been looking for a fix for the last week now.
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Danny80y said:
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Click to expand...
Click to collapse
How do I flash TWRP when Im stuck CWM?
hellshavoc said:
How do I flash TWRP when Im stuck CWM?
Click to expand...
Click to collapse
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Striatum_bdr said:
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Click to expand...
Click to collapse
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
hellshavoc said:
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
Click to expand...
Click to collapse
you hold the volume down until the screen starts, then you let go and wait
whycali said:
you hold the volume down until the screen starts, then you let go and wait
Click to expand...
Click to collapse
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
hellshavoc said:
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
Click to expand...
Click to collapse
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
It is confusing but just keep trying till you get it!! Once there go to the TWRP site they have the file and the fastboot commands all set in a guide.
I have exactly the same problem than you.
I had the fastboot/adb connection (I used to push the rom by adb), but i tried to install a wrong version on gapps. Since then, I'm stock in the recovery mode without adb/fastboot connection.
If you find a solution for that, pleaze post it !!
Striatum_bdr said:
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
Click to expand...
Click to collapse
Hello everyone, been a lurker for some time, but have never needed to post before until today. I'm accustomed to rooting and installing custom roms but I've never had anywhere close to as much difficulty as Im having with this tf201. Heres the situation:
Not sure if you'd call this bricked, as I have total access to fastboot, adb, and CWM Recovery (version 5.8.3.4 touch btw). However my most recent attempt ended with totally wiping from the volume down+power menu (whatever its called). I can not turn the tablet off, as it automatically boots to the asus splash screen (and goes no further, naturally). It is unlocked, and my drivers do work (both fastboot and adb recognize the device), but I can not flash or push anything to the sdcard (with adb its a protocol failure, with fastboot I get "sending zip....OKAY writing zip....FAILED [remote : [FileOperationFailed]]) Don't know if it needs to be said, but I also can't simply drop the file on the sd card as if it were a media storage device as "my computer" does not recognize that it is connected (Oh I am using the naked universal drivers from http://forum.xda-developers.com/showthread.php?t=1998650 )
So yeah, Im at a loss as it seems like no one has had this particular problem before (also my connector cable works fine, so its not that). Any help would, of course, be greatly appreciated.
EDIT: On the tablet after trying to flash with fastboot it returns "Failed to process command flash:zip error (0x30003)"
Really? Not a single person has any idea? Could really use some help here...
GrimAgent said:
Really? Not a single person has any idea? Could really use some help here...
Click to expand...
Click to collapse
You do not flash zips with fastboot.
First of all tell me where your "NVIDIA" logo is when you first power on, bottom center or bottom right?
The nvidia logo is in the bottom center of the "EEE PC Splash"
This is going to sound stupid, but did you verify the MD5 before you tried to flash it?
GrimAgent said:
The nvidia logo is in the bottom center of the "EEE PC Splash"
Click to expand...
Click to collapse
You are still on the ICS bootloader if NVIDIA is bottom center.
Go here http://www.teamw.in/project/twrp2/93 and follow the instructions for "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)"
You will need to get the ICS blob file. Never flash the wrong recovery for what bootloader you are on or you can brick your device.
If you get it working and you want to upgrade to Jellybean bootloader there is instructions in post 2 of the Hairybean Rom thread. "Upgrade instructions for ICS"
edit.. to make it a bit easier for you.
Get this file http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.4.4.0-tf201-ICS.blob
Rename it to twrp.blob
Place the twrp.blob in the same folder as your fastboot exe
Go into fastboot and type
fastboot -i 0x0b05 flash recovery twrp.blob
Wait for it to finish and then type
fastboot -i 0x0B05 reboot
see if that works.
Damn, I had a feeling it was the bootloader issue that I messed up. I went searching all over for how to find out which one I had once I realized my potential mistake. Gonna give these steps a try
I just tried all your steps, twrp is on there and I was able to push both cm10 and gapps onto the tablet, but now the zips I pushed to the sd card arent showing up in TWRP...
GrimAgent said:
I just tried all your steps, twrp is on there and I was able to push both cm10 and gapps onto the tablet, but now the zips I pushed to the sd card arent showing up in TWRP...
Click to expand...
Click to collapse
If you now have twrp on there you dont need to push a file. Place the file on an external SD card on the root and plug it in before starting prime.
When going into TWRP go into install and select external SD. Pick your rom and then flash it.
Thanks a lot flumpster, everything's good now and Ive got cyanogen up and running smoothly. You've brought my tablet back to life and Ive learned a valuable lesson
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Download mfastboot and redownload the recovery img
hetor99 said:
Download mfastboot and redownload the recovery img
Click to expand...
Click to collapse
Thanks.
Decided to install it on my desktop. While trying various files, my laptop accidentally got hit with Chromium virus. It looked like all required files were there, but kept having problems with a couple of those sdk files (tools/platform tools).
I'm still getting the following error:
( bootloader) has-slot :recovery: not found
And once again the Android SDK Tools and Android SKD Platform-tools that are under Tools (preview channel) are unchecked. Not sure if they are needed.
Follow the instructions of how to install on the general section
hetor99 said:
Follow the instructions of how to install on the general section
Click to expand...
Click to collapse
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
L8Show said:
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
Click to expand...
Click to collapse
How to Install TWRP Recovery and Root MOTO E
https://www.youtube.com/watch?v=9Jh-O2LGL3Y
OK, it is done.
Took a couple days with several hours of clicking, and checking settings, and reading and researching, and watching videos, and downloading, and installing/uninstalling, and restarting, but it's now rooted! Way too much time wasted even though it was raining and the gf and I were just watching movies for a lot of it. She kept asking me why I'd waste so much time and remind me I had a perfectly fine iphone nearby. Today I finally got to the point where I had given up. I figured something was screwed up with the phone after that reset on my computer.
Some highlights that may or may not be helpful for the next moto e rooter:
USB debugging was somehow switched to off a few times after I turned it on. Might have been after resetting phone, but who knows exactly.
I set screen to stay while connected via USB.
I removed all the apps I could and took out the sd card.
Kingoroot stuck at 66% many, many times, and then phone would restart. Research showed it may be accessing the wrong ADB instance or something. So I uninstalled SDK, fastboot, Minimal, etc. Anywhere it could have been hiding. Even did a system restore to last week the day I reinstalled windows. Didn't help one bit. Which is to also say... there are a half dozen or more legit options. Try different ones if you are relatively confident you followed directions the 1st 10 times.
Ministro didn't have moto e in their data base.
Finally back to XDA after checking a dozen videos (I have to admit I was completely dumbfounded and was mad at the whole process). I found XDA Kingroot and right away it worked, but it needed permission to allow apps that were not certified or some thing. I can see how people would think this is so easy. If I had started with this, I'd never have had to ask for help here. Btw, was this my problem all along? Did I miss that in the instructions or was it something else possibly? I don't remember if I did that before since it was 3 days ago.
So far I am thoroughly impressed with the this moto e. I paid $40 for it on a whim and now that I can remove a bunch of bloatware and customize it a bit, I think it may be a good gateway into android devices.
Thanks for looking and all your suggestions.
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
faheyd said:
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
Click to expand...
Click to collapse
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
L8Show said:
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
Click to expand...
Click to collapse
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
-z3r0- said:
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
Click to expand...
Click to collapse
Thanks for that information. I thought I saw adb devices command working in fastboot mode in one of the videos so I thought that was the problem. I thought adb needed to root the phone.
In order of what I've done with the phone so far:
Sent/got codes and unlocked moto e.
Turned on developer options and USB debugging.
Was then unable to get TWRP or the other cw something to work using the command fastboot flash recovery (file name) or fastboot boot... commands.
Gave up and installed Kingroot and everything worked fine.
Decided to try to install TWRP and superSU since kingroot had worked. I read that the phone needed to be flashed back to stock to do this and watched/read a couple of guides. http://forum.xda-developers.com/showthread.php?t=2759495
I used the following named file:
SURNIA_ACG_LTE_5.1_LPI23.29-30_cid9_subsidy-DEFAULT_CFC
The phone was changed back, but data doesn't work. I can't access wifi because as soon as I switch it on, it switches back off. 4G, etc is not working either. So after trying to figure that out I decided to just proceed and put TWRP/superSU on the phone.
I powered off the phone. Powered into fastboot mode connected the phone to my computer.
I opened Minimal fastboot folder and shift/right click to bring up the command prompt.
In the command promt i typed fastboot devices and it shows my phone.
I then type fastboot flash recovery (file name or renamed to recovery or renamed to TWRP or I click the actual file and drag it to the command prompt) and then hit enter.
It says it's doing stuff in so many seconds, but after nothing happens. The phone doesn't reset like some of the videos. If I reset it, it powers on, but not into the TWRP screen.
After that I did more reading and found out that adb doesn't always play nice with windows 8.1 and that you might need to force other drivers to make it work right. I did this next and was going to try all the available options from universal naked driver later, but there were no motorola drivers.
Then I came here and learned something new. ADB devices command doesn't work when the phone is in fastboot mode so that has no effect on installing twrp...
Right now I am considering trying to install the other stock files I have access to:
SURNIA_ACG_LTE_5.1_LPI23.29-20_cid9_subsidy-DEFAULT_CFC (20 instead of 30).
After that I am out of ideas if it's not the adb problem. Might kingroot again and go from there.
Ok after researching, it seems that LTE file may not work on sprint and there was success using the boost file from
http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
(2 hour dl make that 5+ lol)
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'll try that next to get the wifi working and then figure out why it won't root.
Thx!
L8Show said:
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Click to expand...
Click to collapse
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
rakeshwipr said:
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
Click to expand...
Click to collapse
and open the command prompt with admin rights
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
d
Thanks! The devices shows up when on as ADB and in fastboot too. I had to take a break when the kernel download took 8 hours, but I think I got the file that will work to fix the wifi issue. I can't mess with it til I get home tomorrow, but I will read and follow all advice.
For the previous poster, I did do the admin rights and did rename TWRP file to recovery... I aslo tried many other combinations, but will keep it in mind for all further attempts.
Appreciate the help so far. I almost left it with the kingroot, but it was bugging me that I couldn't get it to go. Hopefully I'll have good new tomorrow.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
Device shows up in both instances.
It's stock now and the wifi works. Flashed it back to stock by following Mdkcheatz guide here:
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'm stuck where I was when I first started this thread. I've set my account up as administrator. Developer is enabled and so is USB debugging. I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
I confirmed the connection:
fastboot devices
I try to flash it with the:
fastboot flash recovery recovery.img
It says:
target reported max download size of 268435456 bytes
sending 'recovery' (6928 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.359s]
finished total time: 0.578s
C: |Program Files (x86)\Minial ADB and Fastboot>
I'm running windows 8.1 (64 bit). I read that some people had had problems with windows 8. Kingroot worked through the app store. It has been flashed with various stock kernels and that usually takes a few minutes so I don't think it's doing much in half a second. I'll research a bit more, but I think it just a bad combination of this version phone and windows 8.1.
I started the phone after this last attempt. Are there any files in internal storage that I should look for?
L8Show said:
I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
Click to expand...
Click to collapse
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
-z3r0- said:
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
Click to expand...
Click to collapse
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
L8Show said:
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
Click to expand...
Click to collapse
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
-z3r0- said:
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
I am on v2.65. Should I use this version? I checked root and it's rooted, but I needed to use no bloat app (instead of free titanium) to remove some apps. Is that normal? I thought once rooted and set up, I would have complete control. Some apps seem very invasive so I haven't grabbed many yet. I have some questions about apps, etc., but will probably research and ask in another forum if needed.
Thx again for all the help and pointing out my mistake.