[Q] Nexus S 4G Unlocked, Unrooted Broken Recovery - Nexus S Q&A, Help & Troubleshooting

Hi,
I had before the OTA for Jelly Bean an ICS unlocked and rooted.
I tried to use ShabbyPenguin to get it rooted again but now I have a broken recovery.
So not sure what do I need to get it rooted again.. Is it possible?
Thanks!

Not positive, but could u flash cwm through adb? Then just flash a rooted ROM, or supuser.zip. Is the bootloader is still unlocked?
Haven't heard good stuff about root toolkits, its actually really easy to do for our phones.

Not sure if it is possible to flash cwm trough adb... However I will try it later today...
And yes, bootloader is still unlocked...
rustyjay said:
Not positive, but could u flash cwm through adb? Then just flash a rooted ROM, or supuser.zip. Is the bootloader is still unlocked?
Haven't heard good stuff about root toolkits, its actually really easy to do for our phones.
Click to expand...
Click to collapse

Yeah, I am positive u could use adb fast boot to flash a recovery, cwm or twrp u just need the image.

hhhmmmm... no luck yet...
I tried to flash a recovery and it keeps giving me a message
<waiting for device>
After that it seems like stuck..
I read somewhere else that maybe because of the drivers, but I already tried a couple of versions 1.3.8 and 1.5.6 with the same result...
btw I'm using a Windows 7 64 bit machine...
Not sure if use a Linux machine will have any benefit...
rustyjay said:
Yeah, I am positive u could use adb fast boot to flash a recovery, cwm or twrp u just need the image.
Click to expand...
Click to collapse

Well...
Also tried the google usb drivers with no luck....
I guess that I will try it with some other windows/linux version later today...

Off but on topic. Describe what you call a broken a recovery please.

When I try to run the recovery it appears a dead android with a red exclamation mark on the screen....
After that it takes some time to reboot again...
albundy2010 said:
Off but on topic. Describe what you call a broken a recovery please.
Click to expand...
Click to collapse

That is stock recovery. It is not broken.

Yes I was saying it was broken because before the OTA update I had twrp as recovery, and now I can't flash any recovery
albundy2010 said:
That is stock recovery. It is not broken.
Click to expand...
Click to collapse

When you flash/install a ota your recovery gets wiped back to stock once it boots up due to the flash recovery script in the stock ROM.
Nothing is wrong with your device. Just follow a real guide on how to unlock and root. Real meaning using the SDK. Or even use one of those stupid one click crap. should not have a issue.
Guides are in the forum stickies.

Hi Guys,
Well not sure what the problem was.... maybe the drivers, maybe Win7 64 bits or I don't what...
I used a WinXP machine with the pdanet installed and it worked like charm...
I succesfully installed the recovery and root again.
Anyway... thanks for your time.

Glad to hear that.

Related

[Q] boot loop

Hey I hate having to post this but im stumped. i was running cm7 nightly build 21 and wanted to flash back to stock pd15img. i followed the steps but when i went to update all it did was turn s on. now my mytouch gets to the animated MY logo and loops. i can still get to recovery and i have tried restore my backup but i still get the MY animated boot logo. any help or suggestions? thanks.
Did you revert your recovery back to stock or Clockwork 2.x instead of Clockwork 3.x that CM7 requires?
Genocaust said:
Did you revert your recovery back to stock or Clockwork 2.x instead of Clockwork 3.x that CM7 requires?
Click to expand...
Click to collapse
Yep. 2.5.1.2.. I even tried just flashing icedglacier but i still get the animated MYlogo wich continues to loop.
does the phone have to be rooted to fix this? It was prior to flashing the PD15IMG, but like i said when it was done loading the image i clicked update and it just turned s on....
okay so i just made some progress i think. i just flashed icedglacier again and this time it changed the boot logo to the icedglacier boot logo but it still loops.
on the bright side of things i was really tire of seeing the mytouch logo.
theycallmechase said:
Yep. 2.5.1.2.. I even tried just flashing icedglacier but i still get the animated MYlogo wich continues to loop.
does the phone have to be rooted to fix this? It was prior to flashing the PD15IMG, but like i said when it was done loading the image i clicked update and it just turned s on....
Click to expand...
Click to collapse
the PD15IMG is a HBoot flashed image. not via Clockwork's Recovery Manager.
What method did you follow to try and unroot your phone.
We kinda need to know what you did in order to fix it.
If you store the PD15IMG onto the root of the SD card and boot into bootloader it should automatically restore everything to a factory spec.
I unrooted my device by downloading the unroot folder and using visionary and the terminl emulator.
I didnt try to flash pd15img through clockworkmod i just put it on the root of my sd card and let the hboot do the rest once it loaded the image it gave me he update option i chose to update and when my phone came back on in hboot i saw s off and now im stuck in boot loop.
I have to get to work but if you think of anything that could help me out trhat would be awesome thanks guys for reading this in the first place
ps now if i try to load the pd15img it will load the image but there is no update opyion
theycallmechase said:
I unrooted my device by downloading the unroot folder and using visionary and the terminl emulator.
I didnt try to flash pd15img through clockworkmod i just put it on the root of my sd card and let the hboot do the rest once it loaded the image it gave me he update option i chose to update and when my phone came back on in hboot i saw s off and now im stuck in boot loop.
Click to expand...
Click to collapse
Try doing this. Esp. if you did the ./gfree deal.
http://forum.xda-developers.com/showthread.php?t=863899
I also made this mistake, I had to reflash a cm7 rom or miui, downgrade the recovery to 2.5.x (could also adb push) and from there went back to stock and rerooted and flashed ice glacier.
well im downloading sdk now. my internet is super slow.
theycallmechase said:
well im downloading sdk now. my internet is super slow.
Click to expand...
Click to collapse
you are just wanting the ADB you can download and install the drivers for just that. Takes like 5 mins to get up and running.
neidlinger said:
you are just wanting the ADB you can download and install the drivers for just that. Takes like 5 mins to get up and running.
Click to expand...
Click to collapse
cool drivers are installed. so do i just need to be hboot to use the drivers? or is there some sort a software i need?
theycallmechase said:
cool drivers are installed. so do i just need to be hboot to use the drivers? or is there some sort a software i need?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=928370&page=2
neidlinger said:
http://forum.xda-developers.com/showthread.php?t=928370&page=2
Click to expand...
Click to collapse
hahaha thanks bro, love the "(great for noobs)" in the title of the thread. will try as soon as possible.
after reading the guide i have one problem.
5. On your phone go to Settings/Applications/Development and make sure USB debugging is ON and plug it in via the usb..
any suggestions??
theycallmechase said:
hahaha thanks bro, love the "(great for noobs)" in the title of the thread. will try as soon as possible.
after reading the guide i have one problem.
5. On your phone go to Settings/Applications/Development and make sure USB debugging is ON and plug it in via the usb..
any suggestions??
Click to expand...
Click to collapse
Being that you have s=on it's going to be fairly difficult. [sidenote] i still cannot believe the PD15IMG didn't work for you [/sidenote]. but you can try and use the fastboot commands.If s=off you could load a separate recovery image and flash a ROM to get you up and running.
yeah, i knew this would happen to me. when i try to adb in it dosent show my device. i have a thing with best buy where they will mail it in to htc to have it fixed but im not sure since i modded the phone.
theycallmechase said:
yeah, i knew this would happen to me. when i try to adb in it dosent show my device. i have a thing with best buy where they will mail it in to htc to have it fixed but im not sure since i modded the phone.
Click to expand...
Click to collapse
since you are in fastboot you cannot use
adb devices
Click to expand...
Click to collapse
you have to use
.
fastboot devices
Click to expand...
Click to collapse
ok so adb devices gave me a list of devices wich was none.
fastboot devices did not do anything for me.
wait a minute.... it did show something a second time it says sh0bt602653 fastboot....
Ok, that means fastboot has detected your phone. You can flash individual system.img, recovery.img, etc directly from fastboot.
so what do i flash? what commands do i need to use.
C:\adb>fastboot -p sh0b7t602653 update update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
πmªeΩ▲K¡8|x¥►╬←ì☻²╣⌂ì╒▄╞)ⁿ‼♀÷ta in 'h↑τ‼
íTQ▬á╠4δ/l≤huä╘:ì{îC`╢r◄+m§┌╪é^EÇkm☺ªfR
⌠èc┘↕á(╚αñ-0←♫┌╗ê-UY#è°┌o◄■k┤▐╩_``╠FA∞9 ÄM°c↑Sl░LΩ¥♣⌠q╦è╬5è╖P»ìì_j↑û♦ß‼[Γ╞ö¶¡l∙K
╬@↓%$»}ÅKù⌡ΘP9♂₧▒≤☺■Wm3┴pß|*╩°φ`Dú╞▒m└√±←╓6↓A¬]W,ùa½↓εWX╗ôâ\?o\ö~y╚` ╨%█εç←╚q
¶╩♥&ò⌂M─)_5m8ù╢+'⌠y<BWδ¼
!╩X┘♫■s▐k╗wS";öPôBÇ1Yé↔è_ÿ∟╧♫â`↕á┘h▐]∟-╟;»5
▼Ç↨♥H·ò⌠ƒQ²'►╟Oç∙╗Y∟ì▲67╘%)▐∩╘kO¥▬Θî☼R∟┴¼'

i cant do Recovery

hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Snow201 said:
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Click to expand...
Click to collapse
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
FatherD said:
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
Click to expand...
Click to collapse
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Snow201 said:
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Click to expand...
Click to collapse
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
osugsxr said:
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
Click to expand...
Click to collapse
NVM, there is no recovery for HTC at all, only Galaxy and some more. what i need to do?
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
k1llacanon said:
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Snow201 said:
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Click to expand...
Click to collapse
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
k1llacanon said:
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Snow201 said:
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Click to expand...
Click to collapse
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
frdd said:
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
Click to expand...
Click to collapse
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Snow201 said:
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Click to expand...
Click to collapse
If you have working ADB and fastboot working (there is a sticky by user fibsib that explains this) you can make sure your phone isnt really just trying to boot the OS and failing rather than trying to enter recovery with the command
Code:
adb reboot recovery
But anyways figure out which version you have before doing anything more, flash the wrong stuff and you could break stuff. There are good info here as to how to see if you have the Ville=Z520e=S4 processor model or the Ville C2/Z560e/S3 processor model.
Then download a recovery for your phone model and install it with this command from your computer
Code:
fastboot flash recovery nameofrecoveryyoudownloaded.img
Should work.
have you actually flashed a recovery yet?
which one and how did you do it?
Make sure you have your phone updated to the latest software version before you root. Download system update OTA and click update.
Otherwise you will have issues.
I am rooted T-Mobile phone with original software 1.54 and still can not do recovery or update, it is probably me but it is difficult.
If you are in the US, make sure you use the US version in the development section after you upgrade your phone. Update then try to root it might be easier.

[Q] Please Help! Phone Bricked (Noob Problems)

Hey all, sorry if this seems like other questions being posted, but I can not get my phone to work even after attempting the other fixes posted on the forums. I rooted my phone and was running the stock rom that came preloaded with it. I attempted to install CM10 through Rom Manager to no success, so I then tried to manually flash it as well as Gapps. My phone initially got stuck at the CM10 bootloader, but i could still go into CWM Recovery 5.8.3.1. After trying to get the rom to work more, it seems as if all I can access is CWM Recovery and nothing else. My phone wont even boot into the bootloader anymore and all i have access to is CWM Recovery.
I am not the most tech savvy individual when it comes to this since it has been ages since i tinkered with roms, but I would really like to fix this. So heres the facts since my post is so long (sorry!):
-Phone WILL NOT go into bootloader
-Can ONLY ACCESS ClockworkMod Recovery (5.8.3.1)
-SD Card wont mount (I get error "E:Unable to open ums lunfile (No such file or directory)")
I really just want to go back to stock and root again from scratch to reduce any errors like this from occurring in the future and ANY help would be appreciated because I am totally lost and without a phone now. To make things even more difficult, I only have access to a Mac running Lion....although i do have Windows 8 through the use of a bootcamp program, so I CAN run windows programs. Thank you all for any information you may have!
Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app
luxandroid said:
Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I do NOT have a nandroid backup. I dont even have access to my SD Card since my phone wont recognize it. I dont know where to even start in terms of fixing this. Any additional information anyone needs who thinks they can help me can be provided.
Porgress (Sort of)
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!
fragkiller1 said:
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!
Click to expand...
Click to collapse
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.
Progress!
Darknites said:
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.
Click to expand...
Click to collapse
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!
fragkiller1 said:
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!
Click to expand...
Click to collapse
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.
Darknites said:
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.
Click to expand...
Click to collapse
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?
fragkiller1 said:
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?
Click to expand...
Click to collapse
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.
Darknites said:
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.
Click to expand...
Click to collapse
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again
fragkiller1 said:
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again
Click to expand...
Click to collapse
Does the bootloader say fastboot usb?
Darknites said:
Does the bootloader say fastboot usb?
Click to expand...
Click to collapse
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.
fragkiller1 said:
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.
Click to expand...
Click to collapse
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.
Darknites said:
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.
Click to expand...
Click to collapse
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?
fragkiller1 said:
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?
Click to expand...
Click to collapse
I see that you got the toolkit and bootloader working but did you end up using the RUU?
Success!
Darknites said:
I see that you got the toolkit and bootloader working but did you end up using the RUU?
Click to expand...
Click to collapse
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!
fragkiller1 said:
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!
Click to expand...
Click to collapse
Np but this time use TWRP as your recovery and once you up and running with CM10 you can use Flash Image GUI to flash the boot.img if you ever update the rom.

[Q] Corrupt Recovery

Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
the exclamation point is the stock recovery. once you take in an ota, it removes both root and your custom recovery. to get your custom recovery back so that you can flash a bootloader(and the supersu root binaries). you can flash a custom recovery while youre in your bootloader via fastboot on your desktop.
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Yeah just realised that. Sorry its my first post
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
why don't you try twrp maybe you can flash twrp then remove the file then go back to cwm
Sent from my Nexus 5 using Tapatalk
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
luppas said:
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
Click to expand...
Click to collapse
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
simms22 said:
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
luppas said:
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
Click to expand...
Click to collapse
adb version and fastboot devices is different. adb is not fastboot and you can not use adb as fastboot. fastboot is fastboot.
simms22 said:
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
Click to expand...
Click to collapse
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
luppas said:
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
Click to expand...
Click to collapse
glad you got it

[Q] Unlocking problems for the bootloader

I am trying to unlock my photons Q bootloader on the Motosite which is well known. I check it now a million times if I have a typo and I Dont.
The button with the "request unlock key " comes up, I hit it, and didnt recieve any mail. And I started last week doing it.
The Photon q has a GSM mod done by the almighty CornholioGSM, and I am using a connection from Germany. Since it is a Sprint photon, I thought that it might be discarded, because the ip it comes from is german ?..
Would be great to have someone telling me if there is another solution to this ..
I tried to flash with the locked bootloader the recovery, but get the message "invalid image size" on CWM or TWR.
I hope this Q is not too noob for all of you.
I would try motochopper or whatever the exploit was to unlock without Moto's assistance.
It may have been unlocked previously, (relocked for warranty swap) in which case I'm not sure you can use the site to re-unlock the device...
arrrghhh said:
I would try motochopper or whatever the exploit was to unlock without Moto's assistance.
It may have been unlocked previously, (relocked for warranty swap) in which case I'm not sure you can use the site to re-unlock the device...
Click to expand...
Click to collapse
First of all thank your for your answer ! Most likely you are right. Now my Q, I did read Motochopper just install SU and also gives root, but without touching the bootloader. Dont I need to unlock the bootloader if I want to install Cyanogen or any other Mod ? Maybe I understood that wrong.
x11-nice said:
First of all thank your for your answer ! Most likely you are right. Now my Q, I did read Motochopper just install SU and also gives root, but without touching the bootloader. Dont I need to unlock the bootloader if I want to install Cyanogen or any other Mod ? Maybe I understood that wrong.
Click to expand...
Click to collapse
Ok, motochopper did its job. Thank you for that ! ! ! I guess now I have to go on with Goomanager. :good:
x11-nice said:
Ok, motochopper did its job. Thank you for that ! ! ! I guess now I have to go on with Goomanager. :good:
Click to expand...
Click to collapse
If you're wanting to install TWRP, I think they have a new app now... TWRP Manager?
I've always installed recovery using fastboot on the Q, so I'm not very familiar with the apps .
arrrghhh said:
If you're wanting to install TWRP, I think they have a new app now... TWRP Manager?
I've always installed recovery using fastboot on the Q, so I'm not very familiar with the apps .
Click to expand...
Click to collapse
I tried the TWRP Manager, the manager shows me success for installing the TWRP recovery, but I cant access it. It switches back into Fastboot telling me flash failure. Actually I would like to install CM11. Well I will try to install the latest nightly and see whats happening. Hopefully it doesnt brick. :silly: Thanks for your help, I will let you know about success or fail.
x11-nice said:
I tried the TWRP Manager, the manager shows me success for installing the TWRP recovery, but I cant access it. It switches back into Fastboot telling me flash failure. Actually I would like to install CM11. Well I will try to install the latest nightly and see whats happening. Hopefully it doesnt brick. :silly: Thanks for your help, I will let you know about success or fail.
Click to expand...
Click to collapse
You need to install some sort of custom recovery in order to flash a custom ROM.
Open Recovery or TWRP are both fine. CWM is really old for our device, I can't recommend it.
arrrghhh said:
You need to install some sort of custom recovery in order to flash a custom ROM.
Open Recovery or TWRP are both fine. CWM is really old for our device, I can't recommend it.
Click to expand...
Click to collapse
So yesterday Motorola send me the messages with the codes which I apllied for almost 2 weeks ago... I guess the next days will arrive more.
Ofc I tried to unlock and it worked as expected. Now with fastboot flashing tto recovery 2.8.0.1 of TWRP went flawless. Actually I am really impressed how easy it worked, unlike using all the other tools like motochopper and TWRP Manager, which actually didnt solve the problem at all not having a unlocked bootloader.
Now my last Q: Which CM11 is the preferable choice for using it with the Photon. I dont care so much about Nightly or not. What I need is stable VPN and WIFI, and working mail and messenger like Cypher.
And! Thank you so much arrrghhh for all your advice and help. This forum and its users are really a great help to the community of android !
All DONE
Ok used TWRP 2.8.0.1 to install cm-11-20141012-NIGHTLY-moto_msm8960_jbbl and the PA-Gapps-Modular for 4.4.x. Great work on everyone who participated making this possible and developing the necessary tools.
Thanks again to Arrrghhh and Cornholio !

Categories

Resources