The title may sound strange but it's true.
I have this phone for just one week and haven't used it to call (reason: moving from T-Mobile to Tele2, this takes time. Date: 25e).
Rooting will allow me to do some stuff like a different boot animation which caught my attention. What I just don't want to happen is that I brick my phone to the point that it doesn't work anymore. Secondly I void my warranty which is something I don't feel so good about seeing I just got the phone.
I don't know this yet but if I root is. Can I back up everything from the phone? Contacts, Apps, settings etc etc? So when something goes wrong I can install a image of my back up?
Sadly I am pretty dark now. It's all new and while I would like to give it a shot, some things don't feel right for me just yet as stuff is unclear to me on how do it it.
Can XDA help me maybe? Also what are some really cool ROM's? I wanted to get Touchwiz but there is no (lol) and Cyanogenmod is like Stock Android so it seems ...pointless?
Best regards,
Robert Oortwijn
ZyreHD said:
The title may sound strange but it's true.
I have this phone for just one week and haven't used it to call (reason: moving from T-Mobile to Tele2, this takes time. Date: 25e).
Rooting will allow me to do some stuff like a different boot animation which caught my attention. What I just don't want to happen is that I brick my phone to the point that it doesn't work anymore. Secondly I void my warranty which is something I don't feel so good about seeing I just got the phone.
I don't know this yet but if I root is. Can I back up everything from the phone? Contacts, Apps, settings etc etc? So when something goes wrong I can install a image of my back up?
Sadly I am pretty dark now. It's all new and while I would like to give it a shot, some things don't feel right for me just yet as stuff is unclear to me on how do it it.
Can XDA help me maybe? Also what are some really cool ROM's? I wanted to get Touchwiz but there is no (lol) and Cyanogenmod is like Stock Android so it seems ...pointless?
Best regards,
Robert Oortwijn
Click to expand...
Click to collapse
setup adb and learn how to flash back to stock in fastboot. you will never brick your device beyond repair as long as you are capable of following directions for flashing and rooting and such
Here's the sticky from the other forum.
That is very useful and they talk in layman's terms. When I first got my N4, I followed this and got custom everything following the instruction posted there.
I'm no expert, but I rooted my N4 in the first week very easily, and as long as you follow all the instructions in the XDA thread then you won't go wrong. If you are really worried then you can use a toolkit as that will automate everything, but I'd never recommend that as you aren't really learning.
As for backing everything up, you can back up some things like your contacts, WiFi passwords and so on to your Google account. Apps is a lot harder if you want the data, but I believe an ABD backup will work - again, look at the appropriate thread (or use the toolkit for backing up).
And Roms, most of them have a stock feel with more features such as extra customization, but if you want a different look you can use themes - you can get touchwiz themes on the play store for ROMs like CM.
Sent from my Nexus 4 using xda premium
you dont need root to flash roms or kernels, you need a custom recovery(and an unlocked bootloader). you need root to run root apps and to mess around with the root file system.
I agree with tom about the toolkits. There is a large correlation between people who use toolkits and people who break their phone and have no idea what they are doing. Learning fastboot will save you from huge headaches and regret in the future.
username8611 said:
I agree with tom about the toolkits. There is a large correlation between people who use toolkits and people who break their phone and have no idea what they are doing. Learning fastboot will save you from huge headaches and regret in the future.
Click to expand...
Click to collapse
Finally got it rooted and installing CM10.1 went easy!
What I only want to know now is:
How do I relock the phone from rooted to unrooted again? Same for bootloader.
Removal of Clockwork.
And remove CM10.1 and get stock android back.
Thats all!
ZyreHD said:
Finally got it rooted and installing CM10.1 went easy!
What I only want to know now is:
How do I relock the phone from rooted to unrooted again? Same for bootloader.
Removal of Clockwork.
And remove CM10.1 and get stock android back.
Thats all!
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/showthread.php?t=2010312 well, it will show you exactly how to get back to stock if need be.
We were all scared and nervous too when we first rooted an android device. Lol. When you get it done you soon realize how easy it was. :thumbup:
Sent from my Nexus 4 using Tapatalk 2
Can someone help? So I have Cyanogenmod installed on the phone and got USB debug on. When i unplug and go into the bootloader and then plug the micro-usb in my PC doesn't detect the phone. I do have the drivers installed.
It did work, now it doesn't meaning I can't perform the stuff needed.
ps: If your wondering if I use the SDK to put everything to stock well sorry but I can't get the SDK to work. Java issues and errors. Pain in the ass so I stop with that.
In the bootloader and then recovery I get a Android logo with a red /!\ ?
Edit 1: I tried a reboot and now it doesn't hang. The X logo is moving but nothing yet.
Edit 2: 5min later and still at the X logo. It does move but nothing. Is my phone dead?
ZyreHD said:
In the bootloader and then recovery I get a Android logo with a red /!\ ?
Edit 1: I tried a reboot and now it doesn't hang. The X logo is moving but nothing yet.
Click to expand...
Click to collapse
if you are getting and android with a red "!", it sounds like you didnt flash a custom recovery. you need to be on either cwm, or twrp.
edit: it sounds like something got jacked and you need to start over again. it sounds like you are going back to stock, right?
start from the bootloader with fastboot. format/erase all the partitions and reflash everything and you should be golden
im not sure if i reading it right, but from what i can gather, you flashed cm10.1, then found out adb doesnt work right so you are ditching it and going back to stock? i wouldnt worry about it too much. as long as you can still use fastboot in the bootloader, thats all you need to do anything to save yourself from certain death. adb is more helpful for gathering up data if you cant lose it before flashing back to stock
username8611 said:
if you are getting and android with a red "!", it sounds like you didnt flash a custom recovery. you need to be on either cwm, or twrp.
edit: it sounds like something got jacked and you need to start over again. it sounds like you are going back to stock, right?
start from the bootloader with fastboot. format/erase all the partitions and reflash everything and you should be golden
Click to expand...
Click to collapse
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Edit: I'm back in the bootloader. I didn't press the combination right sending me into Download Mode.
Edit 2:
So what I did was this. I followed these instruction on how to install custom ROMS: http://www.androidrootz.com/2013/02/how-to-install-custom-roms-on-nexus-4.html I also followed them in the procedure of rooting your phone.
I tried it out and now wanted to go back to stock. So I found a article also by them and did that: http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
When I was at the point where the cmd said: erasing use rdata the article said: 5min, but it took longer so I unplugged the USB.
Now I'm here where I can't boot the OS anymore. Bootloader does work but recovery doesn't as I get the /!\
Edit 3:
Retrying in the meantime. Now at writing system (done)
Edit 4:
Now I'm at the point where it's erasing userdata....
Edit 5: couple of minutes later and still going.
ZyreHD said:
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Click to expand...
Click to collapse
unplug anything that is plugged into your phone. make sure it is completely turned off. hold volume down and power until it vibrates. it should take you straight to the bootloader
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
yeah something is amiss, hold on let me type this up real quick
go here and download OCCAM factory image. open up the file you downloaded and you should see userdata.img, system.img, etc.... take all the files that end in img and move them to your directory for fastboot aka: /platform-tools, or whatever you use for fastboot.
boot your phone to the bootloader. type this in fastboot, pressing enter after each line:
fastboot format userdata
fastboot format system
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
now for the flashing,
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
OPTIONAL... if you think your radio is messed up -----> fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot
voila
username8611 said:
unplug anything that is plugged into your phone. make sure it is completely turned off. hold volume down and power until it vibrates. it should take you straight to the bootloader
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
yeah something is amiss, hold on let me type this up real quick
go here and download OCCAM factory image. open up the file you downloaded and you should see userdata.img, system.img, etc.... take all the files that end in img and move them to your directory for fastboot aka: /platform-tools, or whatever you use for fastboot.
boot your phone to fastboot. type this, pressing enter after each line:
fastboot format userdata
fastboot format system
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
now for the flashing,
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
OPTIONAL... if you think your radio is messed up -----> fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot
voila
Click to expand...
Click to collapse
I got a different option now. format userdata and I get options. Flash all, erase, update filename etc.
ZyreHD said:
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Edit: I'm back in the bootloader. I didn't press the combination right sending me into Download Mode.
Edit 2:
So what I did was this. I followed these instruction on how to install custom ROMS: http://www.androidrootz.com/2013/02/how-to-install-custom-roms-on-nexus-4.html I also followed them in the procedure of rooting your phone.
I tried it out and now wanted to go back to stock. So I found a article also by them and did that: http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
When I was at the point where the cmd said: erasing use rdata the article said: 5min, but it took longer so I unplugged the USB.
Now I'm here where I can't boot the OS anymore. Bootloader does work but recovery doesn't as I get the /!\
Click to expand...
Click to collapse
When you see the android laying down that is stock recovery. Press volume up and power to open the menu. Then you can factory reset.
Sent from my Nexus 7 using xda premium
El Daddy said:
When you see the android laying down that is stock recovery. Press volume up and power to open the menu. Then you can factory reset.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I only have 4 options there.
Reboot system now
apply update from ADB
wipe data/factory reset....
Oh I got it. It formatted and I rebooted. For now it only shows the X logo. Will go downstairs in the meantime to get something to drink. It might take some time maybe?
THANKS YOU SO MUCH!!!
Just as I wanted to go it booted!!!!!!!!!!!!!!!!! 2 hours of hard search and it was this small thing to do? I was really afraid that I had wiped the factory reset of the phone!!!!
Thank you again, all of those who helped!!!!:laugh::laugh::good::highfive:
nevermind, you were talking about the options in recovery
ZyreHD said:
THANKS YOU SO MUCH!!!
Just as I wanted to go it booted!!!!!!!!!!!!!!!!! 2 hours of hard search and it was this small thing to do? I was really afraid that I had wiped the factory reset of the phone!!!!
Thank you again, all of those who helped!!!!:laugh::laugh::good::highfive:
Click to expand...
Click to collapse
Congrats. That's why I wrote what I did in your other thread. Read, read, read. Its better to know how to fix things before they happen then frantically trying to find out how fix them while they happen.
Sent from my Nexus 7 using xda premium
Related
Last night I was using my Nexus 4 and it wouldn't connect to any web pages so I thought I'd reboot to see if that fixed it. I powered off then back on and it won't get past the Nexus logo on the start up screen.
I'm unlocked and rooted but haven't installed any Roms ever. I used Wug's toolkit to root.
the only thing I can think of is that I was copying fonts from the system folder and maybe I moved a font instead of copying it, but I really don't think moved anything without replacing. Either way, i really don't think that moving a font would cause the phone to not boot up.
The phone booted up just fine an hour or so before this happened, so the font thing is the only thing I can come up with. I tried to use Wug's toolkit to push the font file to the N4 but the script gets stuck when trying to reboot.
Please help!! any suggestions?
------
addt'l info:
CWM not installed, phone does not bootloop, just gets stuck at X
nvillamob said:
Last night I was using my Nexus 4 and it wouldn't connect to any web pages so I thought I'd reboot to see if that fixed it. I powered off then back on and it won't get past the Nexus logo on the start up screen.
I'm unlocked and rooted but haven't installed any Roms ever. I used Wug's toolkit to root.
the only thing I can think of is that I was copying fonts from the system folder and maybe I moved a font instead of copying it, but I really don't think moved anything without replacing. Either way, i really don't think that moving a font would cause the phone to not boot up.
The phone booted up just fine an hour or so before this happened, so the font thing is the only thing I can come up with. I tried to use Wug's toolkit to push the font file to the N4 but the script gets stuck when trying to reboot.
Please help!! any suggestions?
------
addt'l info:
CWM not installed, phone does not bootloop, just gets stuck at X
Click to expand...
Click to collapse
do a factory reset via recovery
by copying system fonts which are not made for jb, your system could be damaged and thats the reason why you are in a bootloop..
What font did you push and how?
Sent from my HTC6435LVW using Tapatalk 2
pa.pn2 said:
do a factory reset via recovery
by copying system fonts which are not made for jb, your system could be damaged and thats the reason why you are in a bootloop..
Click to expand...
Click to collapse
I'd really like to avoid doing a factory reset if possible, but that may be inevitable.
What I did was copy (move?) fonts from the system folder to a folder on the sd card so the fonts would be accessible to something I was making in UCCW.
When I boot into recovery all I see is the Android laying on its back with a red triangle and beneath that it says "No command."
And this is why you don't use a toolkit. It gives you ability to do things when you didn't know how to get there.
You should just factory reset and get your phone booting. I don't think you're in a position to be trying to save your data because you did things without know what was going to happen. Don't ever touch things in system unless you truly know what you're doing. Especially not without a nandroid backup.
Sent from my Nexus 4 using xda premium
I'm in over my head now, but I knew what I was doing at the time. I *think* I moved a ttf file instead of copying it. A brain fart led to all this. Live and learn and hopefully the community can help me out.
I do have a nandroid from a couple weeks ago that I'd be happy to flash but I'm not familiar with adb but I'm willing to give it a shot if anyone could help. Google hasn't brought me much luck.
nvillamob said:
I'm in over my head now, but I knew what I was doing at the time. I *think* I moved a ttf file instead of copying it. A brain fart led to all this. Live and learn and hopefully the community can help me out.
I do have a nandroid from a couple weeks ago that I'd be happy to flash but I'm not familiar with adb but I'm willing to give it a shot if anyone could help. Google hasn't brought me much luck.
Click to expand...
Click to collapse
Best thing I can say is to fastboot flash back to stock. Google on how to do it, there's a guide on XDA on how to restore factory stock images.
Start all over as if you just got your phone and don't do the same mistakes again. Spend the 25-30 minutes and read how to use fastboot, and don't do things without asking or thinking beforehand. If you don't know what you're going to be modifying or whatever, don't do it.
You don't flash a nandroid. You restore it via recovery in recovery mode.
So I booted into recovery, chose wipe data/factory reset.
After that runs, I reboot the phone and I'm still stuck on the X.
I've got the factory image tgz file but I don't know how to flash it
nvillamob said:
So I booted into recovery, chose wipe data/factory reset.
After that runs, I reboot the phone and I'm still stuck on the X.
I've got the factory image tgz file but I don't know how to flash it
Click to expand...
Click to collapse
Use search + read stickies in the future.
Here is the thread you're looking for, http://forum.xda-developers.com/showthread.php?t=2010312
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10l.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.33.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional (NOT optional for n00bs) -- Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Click to expand...
Click to collapse
the files within the tgz will contain those imgs that you need. you may skip on fastboot flashing the radio, recovery, bootloader
do flash the system and boot flash for sure.
thanks again. I must be awful at searching because I can never find what I'm looking for.
In the mean time, I figured out how to use the toolkit to flash the stock image and I'm back in business. i sincerely appreciate the help.
nvillamob said:
thanks again. I must be awful at searching because I can never find what I'm looking for.
In the mean time, I figured out how to use the toolkit to flash the stock image and I'm back in business. i sincerely appreciate the help.
Click to expand...
Click to collapse
It's all good, I mainly use Google and type random tags on google like "how do i restore nexus 4 back to stock" or something between those lines and something would pop up. In general, Q&A there are stickied threads that has an index with a link to all the other pages that you're looking for.
It all comes with experience.
Errrrrrrr. Um.... you kinda killed me when you said toolkit. Don't use them it's what got you in this situation in the first place. Learn from your mistakes. The toolkit didn't necessarily bring you to this situation but you're not familiar with what the toolkit is actually doing and you're doing changes to the system because you aren't aware of what's going on in your surroundings.
http://forum.xda-developers.com/showthread.php?t=1469909 is a good thread on why you don't use toolkits. How do you think I know all this knowledge? Certainly not by using a toolkit. You have to know how to do these things, otherwise the next problem you'll have you'll ask questions some more. Please just take the time and read it and figure it out how to do it. It's not difficult by any means.
Good luck and glad I can help. I hope I could change your mind on the dangers of using toolkits and do it the traditional way with backgrounds of why you're doing this and that. If everyone used a toolkit then no one would be in Q&A forums could help others, like myself. If i used a toolkit, i wouldn't know how to fix your situation either. Thanks.
My Nexus 10 was on Android 4.3 rooted and unlocked. Upgrade to 4.4 via OTA would not work.
I used WugFresh Nexus Rootkit 1.79, and was about to upgrade from Android 4.3 to 4.4, but first ran Flash Stock and unroot so I would be able to accept OTA updates. Unfortunately, the program halted when it completed the requested action, and I am left in fastboot. The tablet is stuck in fastboot mode, and no matter which option I try it always comes back to fastboot mode. Also I have tried to initiate custom recovery, via power and Volume up, but again to no avail.
USB debugging was active, and I had CWM recovery and root.
When I go to 'Restart Bootloader', (or 'Recovery Mode' or 'Start') the tablet immediately reboots back to 'Start'. Thankfully the 'Power Off' button does actually stop the tablet.
I have tried to see if I could get to Stock Recovery from fastboot, but that gives no response beyond going to the next tab.
Is anyone able to provide assistance in recovering from this dilemma?
First make sure bootloader is unlocked, if not
fastboot oem unlock
Then fastboot wipe
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now grab latest twrp or clockwork image
fastboot flash recovery nameofrecovery.img
Then boot to new recovery
For fun format all partitions available to in there
Now go to advanced, adb sideload
adb sideload romofchoice.zip
Then probably need gapps
adb sideload gapps.zip
Now reboot
This will get you up and running, if you absolutely want stock and non rooted let me know and I'll help you get there, but I will advise not to bother with toolkits as most every "help me fix xxxxxx" is from a toolkit user
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
First make sure bootloader is unlocked, if not
fastboot oem unlock
Then fastboot wipe
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now grab latest twrp or clockwork image
fastboot flash recovery nameofrecovery.img
Then boot to new recovery
For fun format all partitions available to in there
Now go to advanced, adb sideload
adb sideload romofchoice.zip
Then probably need gapps
adb sideload gapps.zip
Now reboot
This will get you up and running, if you absolutely want stock and non rooted let me know and I'll help you get there, but I will advise not to bother with toolkits as most every "help me fix xxxxxx" is from a toolkit user
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Many thanks for your response demkantor.
Although I tried to clearly describe the status of the tablet and the problem, I did not intend that I should come across as one who is familiar with the complexities of programming of either the tablet, or rooting around in the registry of a PC.
I can however follow clear instructions.
Your message appears to give a list of what to do, and presumably in the tablet from within fastboot. But I am lost after that.
By the way, the bootloader is unlocked.
Since the fastboot is currently inoperable, how do I initiate fastboot wipe, and then the following 3 commands 'erase system-w, boot & recovery'?
If you can spare the time and expand on your listing, I would certainly appreciate it.
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app
Wow demkantor many thanks! The link you provided will take a bit of reading after I get back from the gym. A full afternoon ahead I suspect! I'll let you know how I go.
Just let me know if you get stuck
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hi demkantor,
All done and dusted. Many thanks for your help, My tablet is now running on KitKat 4.4.2.
Your contributions to XDA University are very well arranged and written, and logically guide us through the maze. I for one did not know XDA University existed, and it is a shame that you as the person who pulled your contributions together have to also point us to it!
Many thanks for your efforts!
Edit - I read somewhere that the [Q] at the start of the thread should be changed to something else when the problem is resolved. It certainly is! Can the moderator correct this for me please?
Demkantor, I think I may have screwed up big time. I am unlocked and rooted, running stock 4.4. I woke up yesterday and had a notification that a system update had been downloaded. I did a temporary unroot and took the update. Which failed. I went into twrp and wiped everything. Still no go.Then, like a dummy I rebooted after it gave me a warning about not having an os installed. It wont do anything now except go into bootloader. I must have wiped twrp, because it wont boot into that or stock recovery. When I plug it up to my computer,I get this message( fastboot status-failInvalid command). I've just about every option in wugs toolkit. I keep getting adb and fastbooterrors. Have I completely hardbricked my nexus 10? I would appreciate it if you could point me in the right direction or let me know if I'm just wasting my time. I've been messing with this thing since around midnight and I'm about ready to start pullnig hair out of my head. Thanks in advance my friend.
@63t061
Thanks for the kind words, ive been busy lately (finals and all) so normally i would helped more personally but im glad you were able to get it all working on your own through research, which is the best way as im sure you have learned much and will be able to share with the next! Great job! As for editing the thread title, just edit it in your first post @moejoe88
Can you post all input output from cmd/terminal as its easier to see the issue. And try not use tool kits
Start with
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
Sent from my SGH-T699 using XDA Premium 4 mobile app
Thanks for replying so quickly. I've had to walk away from it for a little while and get some sleep. I'll get some rest and make a fresh start of it. Again, thanks for the quick reply.
I've tried running terminal and the computer wont even recognize the tablet. I believe the battery is drained because I can get it to the bootloader, but it shuts back off after a few minutes. I'm trying to charge for a while and I'll give it another shot. Thanks again.
I followed the guide from this forum on how to root a Nexus 4, but in the process I think I've broken my phone.
I first tried flashing AOKP and it's GApps, the phone booted fine, and I was able to get to the wifi set up screen, however, I couldn't get wifi to turn on.
So I tried to flash Paranoid Android and it's GApps. But now the phone won't get past the boot screen that comes after the google logo.
I've asked around and Googled around for a solution, but I can't find anything. I've been trying to get this fixed since yesterday.
Can anyone please help me? I just want to be able to use my phone again.
GuyWithBrokenPhone said:
I followed the guide from this forum on how to root a Nexus 4, but in the process I think I've broken my phone.
I first tried flashing AOKP and it's GApps, the phone booted fine, and I was able to get to the wifi set up screen, however, I couldn't get wifi to turn on.
So I tried to flash Paranoid Android and it's GApps. But now the phone won't get past the boot screen that comes after the google logo.
I've asked around and Googled around for a solution, but I can't find anything. I've been trying to get this fixed since yesterday.
Can anyone please help me? I just want to be able to use my phone again.
Click to expand...
Click to collapse
How are you flashing? Adb or a Toolkit?
Edit:: How long did you wait? Sometimes it might take awhile, especially with PA.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
How are you flashing? Adb or a Toolkit?
Edit:: How long did you wait? Sometimes it might take awhile, especially with PA.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I flashed with ClockworkMod.
I left it on from 12AM to 6AM.
GuyWithBrokenPhone said:
I flashed with ClockworkMod.
I left it on from 12AM to 6AM.
Click to expand...
Click to collapse
It definitely shouldn't have taken that long. Can you boot into the recovery?
Sent from my Nexus 7 (2013)
Just put your phone in fastboot mode and flash factory image.
Okay now I have a new problem. I turned the phone off, booted back on and tried entering recovery mode, but now I have an image of an android with a red ! mark.
I was just about to try flashing an older version of the stock.
That's normal for stock recovery, you won't be able to sort your phone from there, stay in fastboot mode. You can use a toolkit to flash back to stock from there if you need it more noob friendly. Otherwise you can use the flash-all.bat script in the factory images.
GuyWithBrokenPhone said:
Okay now I have a new problem. I turned the phone off, booted back on and tried entering recovery mode, but now I have an image of an android with a red ! mark.
I was just about to try flashing an older version of the stock.
Click to expand...
Click to collapse
You mean the android is on it's back, press the volu+ button, press power, and that will take you into the stock recovery.
audit13 said:
You mean the android is on it's back, press the volu+ button, press power, and that will take you into the stock recovery.
Click to expand...
Click to collapse
Oh god thank you.
Okay. I'm trying to reinstall Paranoid Android now. I did the sideboot via ADB.
I couldn't seem to get the stock version of android on it though. I made sure to open the tar file and tried to move the .zip "image-occam-jdq39.zip" onto the phone, but it wouldn't accept it. So I'm trying Paranoid android again.
Edit: I got it booted. But now wifi won't work. Neither the speakers.
It didn't work because that's not how you flash a factory image. You need to be in fastboot mode and flash it from a PC using fastboot program. You used fastboot when you unlocked your bootloaders in the first place. You have stock recovery so you can't flash a custom rom, which is why your adb sideload of PA didn't work.
Like I said before you can use the flash-all.bat in the factory image. It runs the following commands which you can also use manually.
fastboot flash bootloader [path-to-bootloader.img]
fastboot flash radio [path-to-radio.img]
fastboot -w update [path-to-system-image.zip]
If that's too difficult use a nexus 4 toolkit to download and flash a factory image automatically. With your phone in fastboot mode, not recovery.
The above will fix your phone, trying to flash custom roms and system image zip in recovery mode will not.
DrFredPhD said:
It didn't work because that's not how you flash a factory image. You need to be in fastboot mode and flash it from a PC using fastboot program. You used fastboot when you unlocked your bootloaders in the first place. You have stock recovery so you can't flash a custom rom, which is why your adb sideload of PA didn't work.
Like I said before you can use the flash-all.bat in the factory image. It runs the following commands which you can also use manually.
fastboot flash bootloader [path-to-bootloader.img]
fastboot flash radio [path-to-radio.img]
fastboot -w update [path-to-system-image.zip]
If that's too difficult use a nexus 4 toolkit to download and flash a factory image automatically. With your phone in fastboot mode, not recovery.
The above will fix your phone, trying to flash custom roms and system image zip in recovery mode will not.
Click to expand...
Click to collapse
Doing so now. If I had known about this tool before, I probably would have been done with this a lot sooner.
Currently flashing stock and unrooting.
The toolkit is most certainly the way to go. No mess, perfect every time for me.
Sent from my Nexus 4 using Tapatalk
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
Theres a hardware method to boot into the bootloader, this i think you can test, just to see if you can at least get into bootloader.....nothing more
Details in the official nvidia link
http://nv-tegra.nvidia.com/gitweb/?...ob_plain;f=README_SHIELD;hb=rel-22r18-partner
There's a thread here on the "questions" thread with users reporting that the timing of the hardware method can be a pain in the you know where.............might be worth looking into that thread for their experiences in booting the bootloader using the hardware method
Disclaimer:If your brave enough to risk a brick, read on
I suspect this might be the 2.1 stock/twrp issue........current twrp, or current stock dont play nice
Its a good sign that SOMETHINGS loading, rather then NOTHING booting, but dont know if theirs a solution
My analysis of the situation, of what little i know, the -w (wipe) command was expecting a stock recovery but instead got twrp, which is why your in this situation.........maybe, i stress maybe, if you could reflash stock again, you might be able to boot into android stock again and try full android again, leaving out twrp, until a twrp fix is found
Edit
Saying that, if the bootloader is, as i suspect, now using twrp to flash things, then you might be boned....... im no expert on bootloaders, stock "recoveries" and how they work, so i might be wrong on that
Reports around here say that 1.3 stock firmware is the recommended back to stock firmware, apparently, flashing any other firmware versions, bring their own issues.............
From 1.3 stock, use nvidias official OTA to upgrade from 1.3 stock, to 2.1 stock, then try 2.1 full android again...........note, i dont think you can skip firmwares i.e. you have to upgrade to 1.4, then to 2.0, then to 2.1, alot of downloading.......the OTA does'nt give you any other choice
Before doing anything that ive suggested, wait till someone with more experience to come along........i dont want to be responsible for you fully bricking your shield..........just wanna give you an idea of what i think has happened
If worse comes to worse, if you have warrenty, get a replacement
Gd luck........remember, this is an analysis of your predicament of what i THINK might of happened, and what steps, i likely might of entertained.......after looking into it more thouroughly, knowing that i could get a replacement if it went downhill.........so your mileage might vary
Edits
Crappy grammer, further musings, clarifications
Thanks.[/QUOTE]
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
I had something similar about... shield goes booting in recovery and trying delete some cache and keeps repeat and repeat
Hardware boot in fastboot / bootloader mode
Accessing Bootloader via Hardware
Unplug power from the Shield Android TV. *
Wait a few seconds.
Hold down the power button.
Plug in power
Count to three
Release the power button
You should see the bootloader screen.
If you hold it down too long or not long enough, it simply doesn’t work.
Restore Shield Android TV to Stock
P.s. Personally me I followed this instructions and kind of magically got it in bootloader mode. First done by instruction and then just gave up and pressed randomly and fastboot screen appear. Thanks God I had to done only once, if I would do again I wouldn't had patients
Good luck with this, hope you will get sorted
Here will be link about where I got instructions about hardware boot
http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
Sent from my Nokia 3310 using free xda app
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
EDIT with joy : I followed all the steps using that rom and it seems everything worked. I reconfiguring the box now. Thanks for help.
basically the procedure I intend to follow is this part (please confirm it's ok):
To flash this recovery image to your SHIELD, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader. Get
DTB file name to use for flashing for your product(see below):
P.s. maybe Since past fastboot commands failed and I only flashed system from zulu99 I could skip the 'fastboot flash boot boot.img' command so if it fails again I still can attempt the fastboot process again?
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>
puppinoo said:
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
Click to expand...
Click to collapse
You are on the right way with those links
P.s. You can do manual one by one entering or paste and copy those commands or (I'm doing) drag and drop file "flash-all.bat" on cmd previous opened there where you have abd/fastboot etc files and extracted RIGHT FIRMWARE (like shift and right click mouse "open command prompt here"
And after this all sit down and relax
Anyway you are on the right way.
P.s. Hope you download adb fastboot drivers somewhere from Internet !?!
Sent from my Nokia 3310 using free xda app
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk
StarShoot97 said:
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?
theesotericone said:
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?
Click to expand...
Click to collapse
I said it looks like this, I did not say the button is the reason
When I access fastboot it stays there until I manually select an option
ultyrunner said:
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.
StarShoot97 said:
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.
Click to expand...
Click to collapse
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
When stock recovery is installed, I am from time to time able to access it (most of the times it just ends in a bootloop)
If I flash TWRP I can't access it, no matter how often I try
I have factory reset my phone, the stuff on the internal is still there and I want to reach this, as I have my chats, SMS, university stuff and so on backed up on the internal storage
I am trying everything - all the regular adb methods, toolkits, every driver, nothing is working
Sorry if you don't understand my situation, but I am in a pinch right now
You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery and cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Edit2: wrong, see my latest reply
RoyJ said:
You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery. Perform a factory reset again like you already mentioned you did as well as a cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Click to expand...
Click to collapse
I did this already exactly like you wrote, did it again now, and I am still stuck in the reboot loop (boots up to Google Logo, then shuts itself down; repeat)
Can't reach recovery mode either
You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.
Fastboot twrp 3.0.0-0 then try to access it
RoyJ said:
You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.
Click to expand...
Click to collapse
Yes, I think so too. I flashed the phone with the full Stock image, the bootloop is still there.
Looks like my precious is dead
At least I have my most important data like phonenumbers, pictures and SMS saved to the cloud
Gonna RMA it tomorrow
Goodybe my precious, I hope you'll be fine :crying:
Got my device back today, the mainboard was damaged, so I had no chance to get my data from the phone
Hey, at least my warranty has been renewed 'till 2018
StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
Try flashing TWRP 3.0.2-3 or boot into twrp through fastboot. Using
fastboot boot recovery <twrp filename>.img
I think booting to twrp using this command will work.
And here's the link to Twrp 3.0.2-3 , as its not available on Official Twrp page.
https://idlekernel.com/twrp/nexus/twrp-3.0.2-3-angler.img
I had the same problem with my 5X, nothing worked I tried every possible solution described above and more. Nothing. I figured out that there was nothing to loose and followed directions from YouTube videos (links below) and it worked. Used heat gun at max temp for about 2 mins from each side. It's been about 12 hours since then, phone works flawlessly. Here are the links:
https://www.youtube.com/watch?v=SD25mdrgAys
https://www.youtube.com/watch?v=Cqh2x-TGnCY
Be careful handling the motherboard after you heat the first side, let it cool first before you start working on the second side. The same with the second side do not pick it up until it's cool.
5X, Pure Nexus Rom 7.1.2 June 5th security update, Elemental X Kernel,
has anyone found solution to this?????