Related
I was dumb enough to root my phone and try using some custom roms just to get a black notification bar and a couple other things. Thats literally all I wanted. Used Cyan, couldnt get notification bar to change color so went back to original. Anyways thought I'd try flashing the black desire bar or w/e, and failed.
Tries booting up and gets half stuck on the nexus 'X' animation loop. It gets really laggy and studders, never fully completing the loop. So I say eff it after fifteen or so minutes and reboot to recovery. Only it's the stock android recovery, not that clockwork one? So I'm lost, can't flash back to original, and decide i'll just try the factory reset. I have no time for this stuff at this point, and just want my phone so I can talk to people.
Did factory reset/wipe option, and still nothing, stuck on boot. Don't know what to do and I would greatly appreciate some help or advice. Honestly would be so sad if this $500 phone is a paperweight.
Dude relax,
1.First boot to superboot
2.Flash your clockwork (Or any other recovery). DONT REBOOT.
3.Go straight to recovery,
4.Restore your nandroid back up,
--- If you dont have back up then you have to download rom what you want (Stock froyo can be found some where in htc site)
--- Select mass storage option in the recovery and copy there the zip file, then flash it.
Tadaa everything is working again
Read my signature, "unroot / restore your Nexus", and execute. If you have ever updated to FRG83, you might be out of luck and no PASSIMG.ZIP will flash. In this case, you'll need to connect using ADB and run flash_image to flash recovery (most probably you'll get adb shell even if your phone isn't finishing boot - just make sure you run adb shell early enough in the boot). Once you've flashed the recovery, get into it and proceed with a custom ROM. If you flash stock again, your recovery will be lost again. If you didn't set up ADB (enable "USB Debugging" option on your phone) - then you're seriously out of luck. If you have it, but don't know how to use it - spend time reading and understanding "flashing Recovery" guide in the same place from my signature (Wiki), and if you have any further questions along the way - ask here.
You're not booting up because you've screwed up framework-res.apk and possibly some other system files - so you're stuck in boot loop. Need to read and understand what you're doing before you're doing it. It's really not that hard, and not willing to spend enough time understanding things "pays off" if mishaps happen - and they happen.
elkyur said:
Dude relax,
1.First boot to superboot
Tadaa everything is working again
Click to expand...
Click to collapse
He can't boot! Do you read what I read? He's stuck in a bootloop! What boot are you talking about?!
Take your time reading before you rush answering with wrong and incomplete instructions that won't get the OP anywhere. A good portion of mishaps happens because of instructions like these.
This is alot for me to take learn in such quick time to be honest.
I can't even get adb to recognize my phone and i've followed all the steps. My computer makes the noise that something has been plugged in through USB, but nothing else. Under that program to uninstall drivers, I try uninstalling them, but they just stay there, nothing changes.
As for the USB debugging and me being ****ed, I'm pretty sure I left that on.
Maybe it would help me if I told you more about what I know and what I've done.
Literally just followed the step by step instructions from this site theunlockr.com/ to root my phone and use a custom rom.
In the process it made me install PDANet (again probably means nothing, but I don't know).
If adb isn't recognizing my phone, I can't flash using it. Again thank you for the help, as I really am clueless about most stuff like this.
Most of the time when doing anything that could possibly do any harm to a device, I am very cautious. I have hacked several PSP's and didn't think this would be much different...
I read all about the rooting, and knew full well all i wanted to do was get a new notification bar, I didn't really read into the rest as I had no desire or use for that information. Then everything went well, and I learnt how easy it was to go back if I screwed up or didn't like what I had flashed. Not to mention people saying it's near impossible to brick your phone unless your really trying to. Maybe that was just me being ignorant, this could not have happened at a worse time. And I cannot thank you enough for your help thus far.
Thank you for the help. Your guides were very helpful. But unfortunately every step of the way I have run into some sort of problem.
When trying to install the sdk drivers, it won't let me install the amd64 or the i386, but only both of them together. As in it selecting usb_drivers installs (where both of the seperate drivers can be found). I don't know if this is right or not.
When typing in "fastboot devices", "HT036P901361 decives" shows up, but when viewed in USBDeview, 2 of the 3 HT036P901361 drivers show as not connected. The only one that shows as connected is the "vendor specific" one.
Also adb devices, shows nothing.
So again, I'm asking for advice or help.
Edit: So I can reboot fastboot through my computer, but cannot flash anything,
typing in "flashboot flash recovery recovery.img" I get a "cannot load recovery.img".
My recovery.img file is saved on the root of the SD card which is in the phone. Is this the correct way to do it? If so I assume it's still because of the issue stated at the beginning of this post (before edit).
Edit 2: Okay decided to try this
fastboot flash recovery C:\CWrecovery.img (where its located on my hdd), and it starts then says failed infoSignature.
volsey said:
Thank you for the help. Your guides were very helpful. But unfortunately every step of the way I have run into some sort of problem.
1. When trying to install the sdk drivers, it won't let me install the amd64 or the i386, but only both of them together. As in it selecting usb_drivers installs (where both of the seperate drivers can be found). I don't know if this is right or not.
2. When typing in "fastboot devices", "HT036P901361 decives" shows up, but when viewed in USBDeview, 2 of the 3 HT036P901361 drivers show as not connected. The only one that shows as connected is the "vendor specific" one.
3. Also adb devices, shows nothing.
So again, I'm asking for advice or help.
4. Edit: So I can reboot fastboot through my computer, but cannot flash anything,
typing in "flashboot flash recovery recovery.img" I get a "cannot load recovery.img".
My recovery.img file is saved on the root of the SD card which is in the phone. Is this the correct way to do it? If so I assume it's still because of the issue stated at the beginning of this post (before edit).
Edit 2: Okay decided to try this
fastboot flash recovery C:\CWrecovery.img (where its located on my hdd), and it starts then says failed infoSignature.
Click to expand...
Click to collapse
Let's get one thing straight. You need to read more, I guess, because you still don't know the basics - and with the lack of knowledge, it's going to be hard to help you.
Fastboot commands and driver only work when you're booted into bootloader - which is, 3 droids on skateboards on white screen and text menu, get there by booting with trackball or volumedown button pressed.
adb works only when you're booting the OS - which means, you don't touch anything and let the phone boot. Right when boot animation starts, adb should also start.
1. That's correct.
2. Are you booting into bootloader? There should be no other way to view fastboot driver. In that case, DON'T boot to bootloader, just reboot your phone and let it loop, and only then try "adb devices". If it works - use the "flash_image" method to flash recovery.
3. Read (2) above.
4. If your bootloader isn't unlocked (does it show a padlock below Nexus logo when you boot?), you won't be able to flash non-standard recovery through fastboot. You might be able to flash a complete system image through fastboot, though. Download a factory image, FRF91 for example, unzip it, then do "fastboot flash system system.img", "fastboot flash boot boot.img", and reboot.
When you flash something, you should open the Command prompt in the same directory as the file you're trying to flash! Or use full path for the image you're flashing. And it should be on the computer, not on SD card.
If everything fails - just unlock your bootloader and fastboot flash anything you want.
I am using bootloader.
C:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (58570 KB)... OKAY [ 8.293s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.014s
That's the error I'm getting everytime.
I got the system.img from hXXp://developer.htc.com/adp.html, I tried looking for FRF91 but could only find megaupload links, and I had exceeded my limit somehow.
As for adb, still getting no devices when I leave it to boot by itself even though I've:
Uninstalled the 3 drivers, unplugged/rebooted, plugged back in/turned back on, and it automatically installs the wrong drivers again too quickly to do anything about it. I've gone into advanced system settings and checked it to never install system drivers automatically. Tried updating drivers, all say they're up to date.
1)So is bootloader not an option for me? Or is there something else I haven't tried? Why am I getting the signature errors?
2)Is it the drivers that are keeping adb from recognizing my phone? How do I fix this?
Any suggestions?
Ok, looks like USB debugging isn't on. In that case, there are exactly 2 options:
1) from here:
http://developer.htc.com/
Download FRG83 image for Nexus, rename to PASSIMG.ZIP, put on the root of your SD card (you can't use the phone for it, so use SD card reader), reboot into bootloader, it'll ask you to flash system image, answer "yes", wait for it to flash. Keep the phone powered. WAIT.
2) if it doesn't work - you're out of luck. "fastboot oem unlock" it is. Then you can flash whatever you want with fastboot.
I thought I'd do this tutorial because some people still seem to be having trouble searching the forum for answers, even though the forum is still only small, so I thought I'd put everything in one place, these are all the processes I've followed and they've worked for me, here you will find links to all the useful posts and places to find out what you need too..... Also I'll try to make it a little more Noob friendly too
But as always if you turn your phone into a paperweight, don't come blaming me for it, I've personally done everything (apart from flashing a stock rom and that is because I've never needed to) in the tutorial and its worked for me and worked for the majority of people in here and that is because we know how to follow instructions properly
If you are unsure about doing anything in this tutorial... DON'T DO IT... Ask a question here... But dont ask rom specific questions here though!!!
Now this will be for doing everything on a Windows PC. If anyone else wants to add what to do on Linux, Mac etc please let me know and I'll add them...
Now you've obviously come here because you're considering rooting and maybe even putting a custom rom on your phone. If thats not the case there is no point reading on...
Once you have your shiny new Sensation XL the first thing you will need to do is check the build number because we have noticed that a couple of the latest builds have not been rootable. You can do this by going to 'settings/about phone/software information/more'
Check the second post for details of the builds we know of at the minute that you will not be able to root. The only way around this at the minute is to flash an older RUU (Stock Rom) which we know can be rooted. Details of how to do this can be found at the bottom of this post!!!
Once you've either got a rootable build or you have downgraded and before you actually try to root your phone you will need to Unlock the bootloader!! Unfortunately unlocking the bootloader is the only way to be able to put custom roms on your phone.
You can get permanant root but you won't be able to put a custom rom on your phone, so if you only want root you don't need to unlock bootloader. You will need to use v4 from this post... http://forum.xda-developers.com/showthread.php?t=1341127 ... Cheers Shingers
But for recovery (CWM) and the ability to put custom roms on your phone (lets face it you do... thats why you're here ) you WILL NEED TO UNLOCK BOOTLOADER
To do this you will need to go to the HTCDEV website at www.HTCDEV.com then you will need to register an account to be able to unlock your bootloader. Now the Sensation XL isn't listed in the devices that it says can be unlocked so what you need to do is when its time to select your device scroll to the bottom and select 'All Other Supported Devices'. Then you will get the warning boxes pop up asking you if you're sure you want to do it then saying you could void your warranty as well. Once you've clicked ok on those you'll be through to the instructions on how to unlock your bootloader.
Remember how to get your phone into fastboot from the instructions because you will need to do it again, or if anything goes wrong.
But if you follow the instructions properly nothing should go wrong... Its been tried and tested by lots of people...
And just incase you don't remember how to do it... Take battery out and pop it back in, then press volume down and power button together until you see the white bootloader screen and then press the power button to get into fastboot.
Please please please follow the instructions to the letter, because if you don't it WILL NOT work. Its a very comprehensive walkthrough on how to do it so you shouldn't have any problems unlocking your bootloader as long as you follow the instructions... If you're struggling here maybe you shouldn't read any further and leave your phone like stock
Then once you have that done you will need to get root and for that you will need to follow shingers5 tutorial below...
Get the file for rooting here DooMLoRD_v2_ROOT-zergRush-busybox-su.zip
1. enable usb debugging from settings - applications - development
2. plug phone to pc via usb cable - charge only
3. open extracted zip folder and click runme. thats all. (if experience any daemon hanging problems pls install htc sync and plug in phone so drivers are installed. once done delete htc sync and repeat root procedure) PC will open a cmd screen with prompts that you need to follow. The app does rest... So its nice and easy
4. After root is complete pls visit market and update SU app. once done root will be fully functional and eliminate any future FCs
5. Also as an extra tip you can install SU UPDATE fixer from market to update your binaries to 3.0
ALL DONE
If you're struggling with the above instructions, remember that you will need to un-install HTCsync because it interferes with fastboot and rooting...
Then once you're rooted you will need to put CWM (Clockwork Mod) recovery on in order for you to be able to back up your phone and flash custom roms. The custom recovery by Paul O'Brien is the best one to use and is available to download here... http://android.modaco.com/topic/348973-clockworkmod-recovery-5027-unofficial-modaco-edition/
You will need your phone in fastboot again and you will need to find the fastboot folder on your PC (Windows). When you're in the fastboot folder press the left shift button and right click on the mouse and select open command prompt here. Make sure your phone is connected to the PC and is in fastboot. Also make sure that the recovery.img file that you downloaded from MoDaCo is in the fastboot folder too. Get back to the command promt window and type the following
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img (Tip: once you get to the r1 bit just hit tab and it will auto complete the rest of the line)
If you can't get the Paul O'Brien recovery installed (apparantly not everyone can) try the Older recovery from here http://forum.xda-developers.com/showthread.php?t=1348693
Now you've got root and CWM
A lot of people who have come this far will want to put a custom rom on... unfortunately its not completely straight forward. But again there is a way round round it and you should only need to do it once, when you're coming from a stock rom.
Now there is two ways of doing it, but one of the ways doesn't always work so I would suggest that you do it the guaranteed way, it is a little longer but it is guaranteed to work! And this method is thanks to shingers5 in this thread http://forum.xda-developers.com/showthread.php?t=1366238 but I will go through it again here....
1. You cant just flash a custom rom on this phone, firstly you will need the 'Chinese rom' which is here http://hotfile.com/dl/148413075/8990501/runnymede_ax918_111511_101713.zip.html and make sure it is on the SDcard part of your phones memory. Make sure it on the root of the SDcard because it will be easier to find later. Then you will need this rom RCMix3d Runny XL rom from here http://dl.dropbox.com/u/56143145/RCMix3D_Runny_XL_v1.2.zip (thanks to benjamin.j.goodwin) and make sure that is on the SDcard too with the other rom
2. Then you will need to download this file from here http://forum.xda-developers.com/showpost.php?p=19494357&postcount=18 it is the 'Chinese boot.img' and will need flashing from fastboot again. So put the phone in fastboot and extract the 'boot.img' from the 'boot.rar' file and put it in the fastboot folder on the PC. Open the command prompt again and type this... fastboot flash boot boot.img ... This should only need doing once if you're coming from a stock rom.
3. Once you've done that you will need to get into recovery. From fastboot select bootloader and then look for recovery, it should be under fastboot if its worked correctly. Select that and the phone should then reboot and go into 'CWM' (recovery). Once there you will need to use the volume keys and power button just like when you were in bootloader. Go down and select 'Factory Reset/Data Wipe' and select that, the select yes on following screen. This will take a few mins (don't worry if it looks like its not doing anything). After that go down to 'Wipe Cache' and select that. and then go down to 'Advanced' select that and on the following screen select 'Wipe Dalvik Cache'.
People who have used CWM before will know all that, but I'm putting it in anyway
4. Once thats all done you will need to select 'Install Zip File from SDcard' and then you will get another screen where you go to 'choose zip from SDcard' and the you will see all the contents of your SDcard, scroll down till you can select the Chinese rom you put on earlier (remember what it was called) and then select yes to install it. Sit back and wait another few minutes. Once its done select the 'reboot now'. The phone will then reboot again and start to load the new rom up. This will take a while so don't worry. Now once the phone has started you should get the start up wizard and you will just need to skip through it (don't worry about it being all in chinese... its in english). Not everyone needs to install the Chinese rom, some people can just go straight to the RCMix3d rom and install that, but it doesn't work for everyone, so I'm putting this in because it always works when you do it this way. Installing the Chinese rom should only need doing once if you're coming from a stock rom.
5. Boot into recovery again and goto 'Factory Reset/Data wipe', then 'Wipe Cache', then 'Advanced' and 'Wipe Dalvik Cache' and then go back to main screen and select 'Install Zip From SDcard' and then select 'RCMix3d zip' file and install that. Once thats done select Reboot Now and wait while phone boots up again... and VOILA you now have a custom rom Installed.
6. You could either leave that rom on (its a very good rom) or choose to install one of the other custom roms, read through the first few posts of each rom and decide from there whether you want to install that particular rom, or do what I did and install everyone and see which you like best
ANDTopix ... http://forum.xda-developers.com/showthread.php?t=1429241
BinDroid ... http://forum.xda-developers.com/showthread.php?t=1420841
CoreDroid ... http://forum.xda-developers.com/showthread.php?t=1444664
Runnymede XE ... http://forum.xda-developers.com/showthread.php?t=1502570
Or you want a tweaked rom with stock look (also from BinDroid) ... http://forum.xda-developers.com/showthread.php?t=1430794
There is also an ICS based rom available now
WRE 1.5 (Worst Rom Ever) ... http://forum.xda-developers.com/showthread.php?t=1491039
Now if you're having problems with any part of this and/or you softbrick your phone, my suggestion is that you stop what you're doing and either see if you can get your phone on and working properly (if so all is well with the world) or turn the phone off and pull the battery out, pop it back in and see if you can get into fastboot, if you can your phone should (I'm saying should, because I don't know what you've done to your phone to be considering this ) be recoverable. You will need to make sure phone is in fastboot and then get command prompt up in fastboot folder and type this...
fastboot oem lock
That will relock the bootloader so that you can flash a stock HTC stock image (or RUU) back to your phone. Your bootloader WILL need to be relocked for you to be able to flash stock image back to phone. You can find stock HTC roms (RUU's) here http://forum.xda-developers.com/showthread.php?t=1317895
When you're in fastboot and your phone is connected to the PC and you've downloaded the correct RUU for your region (they are region specific) double click on the RUU.exe and that should start the procedure of flashing the stock image back to your phone. I've never needed to do this, so I'm not 100% on the whole process.
Please remember that if you flash a RUU back to your phone, you will lose root etc, it will be like when you first got the phone...
Also remember that these instructions are tried and tested by many of the members in here and if something isn't working please check that you've followed the instructions to the letter, because it could be quite likely that you've done something wrong or missed something out...
Now I've tried to be as thorough and as noobish as I can possibly be, but if you think you can add anything just let me know and I will add it.
Special thanks to shingers5 who did all the work to start off with, all I've done really is bring them all together and Football for getting all the stock roms in one place
Software versions 1.24.709.2 and 1.14.709.2 seem unsupported by current methods of rooting.
The only way aound this at the minute is if you can find an older stock rom for your region you will have to flash that in order to be able to root your phone. You will need to relock your bootloader to be able to flash another RUU (see first post). And remember as we can't get S-OFF at the minute it will have to be a rom for your phones region...
Everything in one place , Thanks !
snear said:
Everything in one place , Thanks !
Click to expand...
Click to collapse
It is still confusing about boot.img and chines rom etc. Is it to be done just once?
Some ROMs say flash the Boot.img file as well. Is it different from what you have mentioned or just the same thing.
I would love to try different ROM but I am not comfortable about how to achieve it.
You will only need to flash the Chinese boot.img once and that is when you're coming from a stock rom. Once you've flashed it and the Chinese rom, then flashed RCMix3d you will be able to just flash any rom without the need for flashing the boot.img again.
I know it seems a little long winded but its the only guaranteed way of getting custom rom on your phone. Some people are lucky enough to be able to flash the boot.img and then flash any rom, but that doesn't always work, thats why I've put the method that is tried and tested as working
[vertigo] said:
You will only need to flash the Chinese boot.img once and that is when you're coming from a stock rom. Once you've flashed it and the Chinese rom, then flashed RCMix3d you will be able to just flash any rom without the need for flashing the boot.img again.
I know it seems a little long winded but its the only guaranteed way of getting custom rom on your phone. Some people are lucky enough to be able to flash the boot.img and then flash any rom, but that doesn't always work, thats why I've put the method that is tried and tested as working
Click to expand...
Click to collapse
Thank you Vertigo for make it clear. I will give it a go now.
And there are enough people around to help the new Guys & Girls with there SXL
Cheers for the tutorial
I've got an s-off sensation xl so was wandering if I can avoid the HTC unlock bit?
Johnston411 said:
Cheers for the tutorial
I've got an s-off sensation xl so was wandering if I can avoid the HTC unlock bit?
Click to expand...
Click to collapse
To be honest I'm not 100% sure. But to be on the safe side it might be worth unlocking it anyway. Unless you're feeling brave and want to try it with out first, Then you could maybe let us know if it does work
I'm guessing if there was a clockworkmod.zip I could flash from the stock recovery I wouldn't need to.
I think I'll be cautious and unlock it
+1 From me ...
I only have 2 questions for now.
If I choose "Sensation", instead of "all other supported devices," Is it wrong?
And I can not open a Command Prompt, when I press the left shift button and click your right mouse button in the fastboot folder.
There is no such option ...
luba6ky said:
+1 From me ...
I only have 2 questions for now.
If I choose "Sensation", instead of "all other supported devices," Is it wrong?
And I can not open a Command Prompt, when I press the left shift button and click your right mouse button in the fastboot folder.
There is no such option ...
Click to expand...
Click to collapse
Yeah I would say so, from what people have said if you pick sensation it doesn't work, it does however work if you pick 'all other supported devices'.
If you can't get command prompt open from that menu, do you know how to navigate to the fast boot folder if you open a command prompt from the start menu?
[vertigo] said:
Yeah I would say so, from what people have said if you pick sensation it doesn't work, it does however work if you pick 'all other supported devices'.
If you can't get command prompt open from that menu, do you know how to navigate to the fast boot folder if you open a command prompt from the start menu?
Click to expand...
Click to collapse
Yes, I know how to navigate to the fastboot folder.
Thanks again!
All this information is in another 3 posts about ROOT, CWM, and Bootloader unlock and i read them before i rooted month ago. Thank you for your work, but personaly i think your thread is little bit to large It would burn my brain if i would follow this doing rooting Maybe for someone is good to have it all in one place.
P.s. I flashed Bindroid ROM after boot.img flashing. Then i flashed Dutchdanny provided flashable stock ROM, now use RCMix, and no problem. Actualy i flashed boot.img twice, but i think its only necessary first time and does not matter which ROM u flash first.
Yeah I know its a big post and that all the information in the first post is a available in other posts, but not everyone is like you and searches the forum for answers. On the whole most people do the same but there are some people who 'can't be bothered' to search for answers and start threads asking questions that have already been answered. I know because I've been answering them.
So I thought that it would be a good idea to put everything in one place so the answers would be easier to find.
Its like I said in the first post that some are lucky enough to flash another rom and it work straight away, but not everyone can (like me), so I posted the guaranteed way to get it to work (just like in shingers5 post) because if I didn't that would create more questions. Also I said that you should only need to flash boot.img once and not you can't flash it more than once.
Its basically an attempt to keep the forum clean and not full of unnecessary posts... that can only be a good thing surely
How do i find fastboot folder in my pc ... Or do i hve to create myself??????
Sent from my HTC Sensation XL with Beats Audio X315b using xda premium
MOEHEET said:
How do i find fastboot folder in my pc ... Or do i hve to create myself??????
Sent from my HTC Sensation XL with Beats Audio X315b using xda premium
Click to expand...
Click to collapse
Have you installed the Android SDK like it told you to on the HTCDev website. If so just search for fastboot.exe on your computer. Its all clearly explained when you go through the process of unlocking your bootloader at HTCDev.
Download Android SDK here http://developer.android.com/sdk/index.html
Edit: Attached pics to make it a little easier
Ok got it..thnx 4 ur help...
Much appriciated ..
Ta
Sent from my HTC Sensation XL with Beats Audio X315b using xda premium
hi all ,
i have try to unlock my bootloader since january and have the same problem all the time .
the process keep lock at
"H:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)..."
i have tried to reinstall sdk , htc pilot , ect ect but it s the same problem
please help me
my phone it root with DooMLoRD_v2_ROOT
voileuxcool said:
hi all ,
i have try to unlock my bootloader since january and have the same problem all the time .
the process keep lock at
"H:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)..."
i have tried to reinstall sdk , htc pilot , ect ect but it s the same problem
please help me
my phone it root with DooMLoRD_v2_ROOT
Click to expand...
Click to collapse
Your phone is not permanantly rooted if your bootloader is still locked. Try un-installing HTCsync because that can interfere with fastboot. Also have you put the unlock_code.bin file in the fastboot folder?
Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.
limache said:
Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.
Click to expand...
Click to collapse
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium
Quis89 said:
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.
Toxicoblivion said:
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.
Click to expand...
Click to collapse
It's thought this is a safety feature so that you can't accidentally long press power and restart in dark places like your pocket.
@rider5512 Sounds right to me. Thanks for clarifying.
Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?
limache said:
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?
Click to expand...
Click to collapse
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.
crushalot said:
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.
Click to expand...
Click to collapse
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
fastboot erase cache
limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.
crushalot said:
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.
Click to expand...
Click to collapse
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".
limache said:
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".
Click to expand...
Click to collapse
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?
crushalot said:
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?
Click to expand...
Click to collapse
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.
I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium
hardstuffmuc said:
I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
limache said:
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.
Click to expand...
Click to collapse
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.
limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
crushalot said:
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.
Click to expand...
Click to collapse
Hmmm okay so the other poster's suggestion was to get an OTG cable (a micro usb to USB cable right?) and connect the USB with the ROM directly the phone. Do you think this would be a big difference or no? I just don't know if the issue is the internal storage itself or the mode of pushing the ROM.
Otherwise, I'm pretty much scratching my head and have no idea what else I could do =/.
Just for anyone else who's having issues, I've tried using TWRP's install function with the OTG cable but it still doesn't mount. Just letting people know.
if you are noob to recover your phone you can try some services like this
i revived my HTC one by them
http://goo.gl/1DMXlq
( I posted this elsewhere, but i guess its beter in the actual HTCONE section) , mod feel free to delete my other one, thank you.
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
OnlyEYEShine said:
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
Click to expand...
Click to collapse
Here is a TWRP nandroid backup. You will have to put TWRP 2.6.3.3 on your phone. You will unzip the file and the resulting folder you will put on your phone in the following directory: //sdcard/TWRP/BACKUP/<Serial #>/<Name_of_folder>. If you are not able to get TWRP on your phone and the folder on your phone then you will need to find a Windows machine. Here is what you will need to do:
** Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp. Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone.
** Go to your bootloader. Do:
Code:
fastboot oem lock
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip C:/mini-sdk/rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time. Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
** Then, you reboot. Do:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
majmoz said:
Here is a TWRP nandroid backup. You will have to put TWRP 2.6.3.3 on your phone. You will unzip the file and the resulting folder you will put on your phone in the following directory: //sdcard/TWRP/BACKUP/<Serial #>/<Name_of_folder>. If you are not able to get TWRP on your phone and the folder on your phone then you will need to find a Windows machine. Here is what you will need to do:
** Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp. Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone.
** Go to your bootloader. Do:
Code:
fastboot oem lock
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip C:/mini-sdk/rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time. Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
** Then, you reboot. Do:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
Click to expand...
Click to collapse
Thanks for the info !!!,
But right off of the top, i am confused. I am currently downloading TMRP nandroid back up, as you said in beginning. Thing is i am unaware how to get that file onto my phone. Since it is stuck on the recovery page.... (DL is going to take a while on this machine), But if this fails, ill probably end up just tossing the phone, as i dont know anyone , nor have access to a PC machine. Sadly.
update - will attempt to push this thru via Terminal / adb will keep u posted !
-Update .. @majmoz well, i got hold of a PC laptop, did an adb / fastboot installed, dl'd the RUU, but i cant find the file from it after running the RUU. I even did cmd - Echo %temp% to make sure i was in the correct temp folder etc. Searched every sub folder there , and no zip files , or android.txt files was found . and i sorted them as u said as well.
Will continue trying tho...
Updated again - Well this time as RUU was installing again, i went to the temp files faster, and found 2 files Rom_01 & Rom_02 both zip files. But was unable to find any android text file. So now im at a standstill.
OnlyEYEShine said:
update - will attempt to push this thru via Terminal / adb will keep u posted !
-Update .. @majmoz well, i got hold of a PC laptop, did an adb / fastboot installed, dl'd the RUU, but i cant find the file from it after running the RUU. I even did cmd - Echo %temp% to make sure i was in the correct temp folder etc. Searched every sub folder there , and no zip files , or android.txt files was found . and i sorted them as u said as well.
Will continue trying tho...
Click to expand...
Click to collapse
The RUU Update Window should still be on the computer when you are looking for the files. Once the RUU goes past the first screen, the folder will be erased. You should also sort the /Temp folder by date so the most recent folder is at the top.
majmoz said:
The RUU Update Window should still be on the computer when you are looking for the files. Once the RUU goes past the first screen, the folder will be erased. You should also sort the /Temp folder by date so the most recent folder is at the top.
Click to expand...
Click to collapse
If i would of refreshed the page i would of seen your response, as i just re-editted my last post. with another update. =0)
I found 2 files with rom, Rom_01 & Rom_02 , both are zip files. but i cant find any android text file .
another thing, i am trying to find adb devices , but it is not locating my phone . I was able to earlier reboot into bootloader , etc. Now it tells me repeatedly that device is not found , i have tried adb kill-server, start-server etc. .. and phone is still on cyanogen simple recovery screen . .
Thanks again for ur time & help .. .definetly is appreciated !
OnlyEYEShine said:
If i would of refreshed the page i would of seen your response, as i just re-editted my last post. with another update. =0)
I found 2 files with rom, Rom_01 & Rom_02 , both are zip files. but i cant find any android text file .
another thing, i am trying to find adb devices , but it is not locating my phone . I was able to earlier reboot into bootloader , etc. Now it tells me repeatedly that device is not found , i have tried adb kill-server, start-server etc. .. and phone is still on cyanogen simple recovery screen . .
Thanks again for ur time & help .. .definetly is appreciated !
Click to expand...
Click to collapse
Keep both ROM files and save them for future use. Since you are able to use the PC, I would just run the RUU from the PC. Then in the future try to figure out how to run the two ROM files on your Mac. Just start the RUU again and let it do its thing.
majmoz said:
Keep both ROM files and save them for future use. Since you are able to use the PC, I would just run the RUU from the PC. Then in the future try to figure out how to run the two ROM files on your Mac. Just start the RUU again and let it do its thing.
Click to expand...
Click to collapse
Hey hey , good morning. Had some errands to do last nite then fell asleep. Going to attempt this again today . Oh, and i did run the RUU on the PC so thats where ill keep them also.
Will attempt to see if i can even connect to the phone with ADB, it seemed as if i was unable to last nite.
-update I got the phone to load to bootloader, & to fastboot usb I will try now to attempt this after coffee.. =0)
HAHAHAHHAHA ,, Oh man. Ok well being that it was pretty late last nite, and i had just woken up earlier .... I didnt realize that the RUU actually does the entire process on the PC. and that i DIDNT need to use cmd., and adb etc.
I want to thank you a TON @majmoz With my day or two of aggravation , then to just not get it right last nite.. I think i wasnt there mentally to actually read and pay attention.
My phone is in set up mode now. So i am 99% sure it is all good... Again, thanks , i definetly appreciate it !
OnlyEYEShine said:
HAHAHAHHAHA ,, Oh man. Ok well being that it was pretty late last nite, and i had just woken up earlier .... I didnt realize that the RUU actually does the entire process on the PC. and that i DIDNT need to use cmd., and adb etc.
I want to thank you a TON @majmoz With my day or two of aggravation , then to just not get it right last nite.. I think i wasnt there mentally to actually read and pay attention.
My phone is in set up mode now. So i am 99% sure it is all good... Again, thanks , i definetly appreciate it !
Click to expand...
Click to collapse
Glad you are back in business! :good:
@majmoz Hey i tried sending a PM earlier . but i see it never went thru in my sent Messages.
Just wondering if you can help me one last time. As i stated, i MUST have tmobile wifi calling. I initially had my bootloader unlocked months ago, and only rooted it few days before this brick issue.
Now since i did this process to fix the phone, i see bootloader = Relocked.
I dont want to add any custom roms etc, I simple want to root the device again. I know when i just did it , it was quick n easy and simple. But as im googling for the process now, i cant seem to find any that is similar to what i just did a few days ago. The processes seem extremely long. I think i just added a superuser apk of sorts , and it rooted.
Thanks again !
OnlyEYEShine said:
@majmoz Hey i tried sending a PM earlier . but i see it never went thru in my sent Messages.
Just wondering if you can help me one last time. As i stated, i MUST have tmobile wifi calling. I initially had my bootloader unlocked months ago, and only rooted it few days before this brick issue.
Now since i did this process to fix the phone, i see bootloader = Relocked.
I dont want to add any custom roms etc, I simple want to root the device again. I know when i just did it , it was quick n easy and simple. But as im googling for the process now, i cant seem to find any that is similar to what i just did a few days ago. The processes seem extremely long. I think i just added a superuser apk of sorts , and it rooted.
Thanks again !
Click to expand...
Click to collapse
Here is a step by step guide with pictures. This is called the HTCDev method and it is pretty standard. It just looks like a lot of steps but it isn't that bad.
majmoz said:
Here is a step by step guide with pictures. This is called the HTCDev method and it is pretty standard. It just looks like a lot of steps but it isn't that bad.
Click to expand...
Click to collapse
Gotcha, will try this in an hour or so . Have some errands to run. Thanks again !
OnlyEYEShine said:
Gotcha, will try this in an hour or so . Have some errands to run. Thanks again !
Click to expand...
Click to collapse
Keep this for future reference on how to flash the two RUU ROM zip files:
From nkk71's SuperGUIDE to returning 100% back to stock - Post #1211
http://forum.xda-developers.com/showpost.php?p=55921790&postcount=1211
How to flash two RUU ROM zip files
Code:
[B]fastboot oem rebootRUU
fastboot flash zip RUU_ROM_1.zip [COLOR="Red"][I]<-- hboot preupdate[/I][/COLOR]
fastboot flash zip RUU_ROM_1.zip[COLOR="Red"][I] <-- rest of the files in "1"[/I][/COLOR]
fastboot flash zip RUU_ROM_2.zip [I][COLOR="Red"]<-- files in "2" (kernel, touchscreen drivers 2, wipe userdate)[/COLOR][/I]
fastboot reboot-bootloader
[/B]
Click to expand...
Click to collapse
so i spent over 10 hours trying to figure out how to root, how to install twrp, how to install rom and it was a almost sleepless night.
So lets begin starting with unlocking the bootloader. Files need are the onetool, installed mine with the setup/update/install drivers. Next your phone settings/about phone/tap build number untill developer/settings/system/devp options/click oem unlocking/yes/advancereboot/usb debugging. Now hold down power button to see extended options and click bootloader...this is also know as fastboot. Once it boots itll show info about ur phone and start. Open the allinone tool thingy and click check and select oneplus 7 pro so that both are green/unlock bootloader and follow promot on phone and screen/then check bootloader to make sure its unlocked. It will format your phone..skip the intro and renable oem usb and advance boot and go back to the bootloader.
followed this video https://www.youtube.com/watch?v=69VE4aBQnO4
download the adb fastboot link he has, and from i had to learn insert any usb u can use and install the adb fastboot on that usb
then follow the commands 4. Now you should check which slot are you using with this command "fastboot getvar current-slot" 5. Now you should change the slot in use with this command "fastboot --set-active=*" you should replace with the slot is not in use, for example if you are using slot a the command will be "fastboot --set-active=b". (thats fastboot space dashdashsetdash, also got stuck here)
download the https://forum.xda-developers.com/oneplus-7-pro/development/25-05-romaur-v1-0-fast-stable-t3933394 img /Install this boot.img on fastboot- thanks to wzsx150 and put that iso in the usb with the fastboot installion. This is why no directy w.e found i ran into. Once the img is in there you can click the cmd promot there and itll open the fastboot then you type fastboot flash boot boot_9.5.4.img it should say connected and sent complete. hit volume down and boot to recovery with power button to see le.team twrp3.3.1-0527. click wipe/format data/ type in yes/ wipe done. click back arrow to get to main screen. click advanced/install root. The install should be success but make resure u dont reboot but click back again. click mount. Date should be selected and you should be able to plug in phone to add the rom you want to flash. then click back again to menu screen and click install. if all the way at room look for sdcard folder and there should be your rom you just transfer. in my case i used RomAur-v1.1- [28/05] - [OOS_9.0_9.5.5]-[OP7_PRO]-FAST-STABLE and it installed in 5 mins, didnt get no error 7. Then i hit reboot and let it go...rebooted 3 times and here i am on the rom after trying 10 hours
p.s all the work goes to the ppl who did this, i just had to catch on how to do it...was real painful getting closer and closer but the rom didnt want boot or some other problem that was listed in comments
Honestly this wasn't needed as there are step by step easy enough for a 4 year old to follow instructions for each topic, Root, TWRP recovery and how to recover from a soft or hard brick. This is actually harder to follow as it just looks like a massive run-on sentence. Doing a post like this every step should be separated into bullet points (just some constructive criticism)
Well I started with python script to make own booting for the. 6 update to fix verizions restricted caller. That didn't work out, then I read the magisk option and patch the img. Then fastboot was a big issue 2 of where to put the files, even following the video along it still said wrong location file not found. Then one point I had magisk full install but twrp would start loop to recovery and refused to load twrp. Then I had twrp but not magisk, and the twrp was root locked. One thing that was highlighted was that it was explained just follow the links etc. To me it was like a multiply choice test with 6 options and I got the answer for each option but not 1 option was perfectly smooth. Fastboot! OK where is the fastboot option, I see bootloader though. Small important details were left out.... Back in my day you used Odin, flash root flash twrp and done. Installed Roms via twrp and format worked and twrp always had root access
Eric214 said:
Honestly this wasn't needed as there are step by step easy enough for a 4 year old to follow instructions for each topic, Root, TWRP recovery and how to recover from a soft or hard brick. This is actually harder to follow as it just looks like a massive run-on sentence. Doing a post like this every step should be separated into bullet points (just some constructive criticism)
Click to expand...
Click to collapse
I totally agree with Eric here. Next time you do this, recommend if you are going to put up a "step by step" post, put it in bullet form. This is nearly impossible to follow. I am glad you figured it out, and I also understand the need to vent sometimes, but it doesn't read very well.