Okay, I've done all I know to try and fix my issue, now I must reach out for help. Okay, everything was running normally until I booted into SafeStrap 3.12 and tried to restore my backup. Before the restore I made the mistake of hitting Format system using mr-rf or whatever it's called. So I did the restore successfully but now my phone wont boot past the Motorola red circle. The SafeStrap boot menu pops-up but that screen is unresponsive. I try to select Recovery or Continue but neither work, it just tries to continue I guess but nothing ever happens. I can get to AP fastboot and try to flash the 4.0.4 or 4.1.1 fastboot files through RSDlite 6.1.4 but it gets stuck at the first thing it tries to flash, I think it's gpt_main0.bin it gets stuck at. I don't know what else to do? This is my company work phone and I'll be up crap creek if I cant fix this. I can even get into the stock recovery but nothing I try works. Oh, and in the fastboot files, I read somewhere that cI have to delete the lines with "oem" and "getvar" in them, so I did that but still no-go. Any suggestions would be great.!! TIA>>
Did RSD actually say that it failed at the step you are talking about? If not, I would try it again and let it go, no matter how long it takes, until it says the step failed or fastboot is complete. Go over to Razrforums.com and look up the "All things Root" thread in Razr M section. There are procedures for recovering with fastboot, and there are files there for JB and ICS. Good luck, and get back to us if you get things resolved.
Related
Some backstory first:
There I was, happily running Villain 5.3, complete with apps2sd, and the latest radio. So happy in fact, I decided to ring my friend to tell him about it. So I opened up the dialler, typed "col" and the phone hung on me. So I rebooted it, got stuck in a boot loop.
No problem I thought, I have just installed the vanilla lockscreen, I bet that has something to do with it, so I booted into recovery, and tried a nandroid + ext restore.
It said it was restoring, but the screen simply filled with the progress dots, and continued to do so until the battery died.
Then to my horror, after a recharge, the recovery image is unable to detect the SD card. “E:Can’t mount /dev/block/mmcblk0 [...] Can’t mount sdcard”
It may be worht mentioning, I tried a full wipe, but the progress bar that usually progresses didn't. The on screen status did change from wiping system to wiping cache, but once wiping was finished, the phone hung again, requiring me to pull the battery.
I did some research on potential remedies, but adb devices can't see any devices. Fastboot devices does, but as soon as I try to boot a recovery image, I get error: remote access not allowed, or something similar.
I even tried renaming a rom.zip from an RUU to HEROIMG.zip and loading hboot, but nothign happens.
After much jiggery-pokery I have finally figured out how to get an RUU to actually connect to my phone, but once that is running I get Fail-PU on every part of the update except the radio.
I really can't see any other solution to my problem, either thinking myself or trying advice I find sprawled across the internet, and I can't get t-mobile to fix it because I have invalidated my t-mobile warranty by putting a stock rom on, and the manager of the shop refused to acknowledge I have a right to repair under the sale of goods act.
Any help would be appreciated, and any information desired will be forthcoming.
EDIT: Oh yeah, whenever I start an RUU, it says "Current Image: Error_main (too many links))"
If you are getting remote not allow in fastboot, its a problem witj a perfect spl I think? Failing that try the command fastboot erase userdata -w this should basically do a factory reset on the device
FAILED (remote: not allow) on that too I'm afraid.
I tried the key combo for the factory reset, nothing much happened there unfortunately.
you will have to look into making a goldcard i am afraid :'(
Check here and be patient i had to make it 3 times to get mine to work.
Also i had to use a different RUU to what jesterz suggested,let me google that for you....
www.lmgtfy.com
Good luck!
Ha, I tried every RUU but that one, annoyingly.
I was thinking I'd be knackered as my phone can't connect to adb, but fortunately I still have the generated goldcard image sat in my gmail account, so I'll get right on making a goldcard.
Thanks!
just a guess here..
sounds like...
the SD card might be bad / flaky....
An update!
I don't know if my phone would ever boot after I did this, but I tried it anyway:
fastboot oem rebootRUU
fastboot flash zip rom.zip <----- T-Mobile ROM (all others seem to throw up customer ID error.)
So now, as far as I can tell, I have an (almost) complete system loaded onto my phone under the partition "zip" (I say almost, because userdata won't flash).
However, due to userdata not flashing, I'm stuck in the RUU bootloader bit with the picture of a ROM chip and a big, red cross through it.
Anyone have any ideas how to get out of this screen, without ADB or an SD card (I tried 3, none would mount), or a recovery image because even if I could boot into it, it is now no longer a custom one. All I need is userdata to flash, and I'm good to go.
Also, would my phone actually boot as I flashed everything into "zip," a partition that I just made up.
Had a similar nightmare once. Solved it completely and documented it on the MoDaCo forum, so you may want to give it a try. Google for "No ADB & No SD" and see my post #81 from April 4. Good luck!
Basically the jist of the story goes like this.. I was on the TBH official full gingerbread rooted OTA and i decided to try out a different rom so i made a backup and flashed it... the new rom i flashed i ended up not like it so i said ok whatever ill just nandroid back to my backup i had made.. so i nandroid back to my backup and im getting crazy force closes everywere and then my bootstrap dosent work anymore
So then i say ok ill just SBF it not a big deal.. So i proceed to flash the official .340 SBF file with RSD and it goes through the entire process... it flashes the entire thing fine and does all the checksum matches ETC and they all pass.. then at the VERY end of the process im talking like 99% done when it says "Switching to BP Pass Thru Mode" it FAILS and stops the entire process... I then proceed to unplug my phone and even if i pull the battery or do anything whatsoever it goes straight to the bootloader screen
I tried flashing it again... it always works and is perfectly fine up until 99% where it says switching to BP pass thru mode and then it fails and is over with... I even tried the gingerbread SBF file and nothing is working and the phones stuck at the bootloader screen with the "Code Corrupt" message
What can i do here? Ive never had problems with RSD and SBFing in the past and its always worked on this machine... Im also a little hesitant to bring it into verizon or something with this problem because its stuck on the bootloader screen which is obviously something im probobly not suppose to even know exists
Also i have no access to stock recovery or anything whatsoever
Joe92T said:
Basically the jist of the story goes like this.. I was on the TBH official full gingerbread rooted OTA and i decided to try out a different rom so i made a backup and flashed it... the new rom i flashed i ended up not like it so i said ok whatever ill just nandroid back to my backup i had made.. so i nandroid back to my backup and im getting crazy force closes everywere and then my bootstrap dosent work anymore
So then i say ok ill just SBF it not a big deal.. So i proceed to flash the official .340 SBF file with RSD and it goes through the entire process... it flashes the entire thing fine and does all the checksum matches ETC and they all pass.. then at the VERY end of the process im talking like 99% done when it says "Switching to BP Pass Thru Mode" it FAILS and stops the entire process... I then proceed to unplug my phone and even if i pull the battery or do anything whatsoever it goes straight to the bootloader screen
I tried flashing it again... it always works and is perfectly fine up until 99% where it says switching to BP pass thru mode and then it fails and is over with... I even tried the gingerbread SBF file and nothing is working and the phones stuck at the bootloader screen with the "Code Corrupt" message
What can i do here? Ive never had problems with RSD and SBFing in the past and its always worked on this machine
Click to expand...
Click to collapse
in the stock recovery do a factory rest...that will fix it
I have no access to stock recovery
Stock Recovery
Home+Power Button
Search to enter the menu and volume up+down to navigate and camera button to select
Ok. Problem, my brother in laws phone is stuck at bootup and stays. Tried to back up, to the back up and still stays stuck. Tried factory reset. And still nothing... Stuck. Any suggestions? Pls help and thank you in advance.
*WALK in the WORD*
SBF
dhaymond said:
Ok. Problem, my brother in laws phone is stuck at bootup and stays. Tried to back up, to the back up and still stays stuck. Tried factory reset. And still nothing... Stuck. Any suggestions? Pls help and thank you in advance.
*WALK in the WORD*
Click to expand...
Click to collapse
Put phone in bootloader mode power+volume down+camera and SBF to 2.3.340
Please delete, Ive fixed it
Backmankiller said:
Ok first let me start by saying im sorry if this is in the wrong thread or a repeat. Ok so heres the issue, I had my phone rooted and had a custom rom on it. I downloaded a animation and boot screen and installed them. I had to reboot my phone, when done so it was stuck on the new boot screen for a long time. I tried turning off and on several times each with the same results. So i went into my recovery screen and wiped the the system and and did a factory reset. Im on twrp recovery. I rebooted my phone and it tells me no OS. I have no back up now and dont know what to do. Ive tried using the toolkit to go back to stock but it wont let me saying it cant extract the files. Does anyone have any ideas what to do please? I can get into fastboot mode, download mode and recovery but thats it! Please please please help lol!!!
Click to expand...
Click to collapse
this is exactly why people need to learn adb commands and push commands. you are not bricked. you wiped your system you should have just did a factory reset. as far as the tool kit not extracting I don't know what that's about. stop relying on tool kits. they make things easy yes. but it takes the learning curve away
http://forum.xda-developers.com/showthread.php?t=2010312
If you can get into fastboot you are NOT bricked.
Read up on how to manually flash files in fastboot.
I got it, thanks guys!
Hey all, I figured it was time to make a post and see if anyone could help figure out what I'm missing.
So I recently got my G2 and rooted it, then I installed Team Win Recovery Mod (on accident, actually. Was intending to install Clockwork, but figured it wouldn't hurt anything and it was working fine). Anyway, moved on to install Cyanogen Mod and gapps following the usual factory reset -> flash from /sdcard/ approach. Unfortunately on reboot, it went into fastboot mode.
Since then I've read a ton of stuff about fastboot, and I've reflashed recovery, boot, and system a dozen times, but I'm still stuck in fastboot mode. I've grabbed the CWM for LG G2 (AT&T) from http://www.clockworkmod.com/rommanager and the latest stable Cyanogen Mod from http://wiki.cyanogenmod.org/w/D802_Info. Sadly everything I've seen just tells me to do what I did - reflash recovery and tell it to reboot. I've also tried the "volume down + power until logo, then release and re-hit" method of getting into recovery mode, but the logo is present for literally less than a second, so I just end up back in fastboot.
Perhaps I need to find an flash a stock OS first? The thread on returning to stock firmware scares me :/ http://forum.xda-developers.com/showthread.php?t=2432476 Edit: I gave in and tried playing with this anyway. No good, I can't get the phone to enter "download mode", no matter what I do, it reboots into fastboot.
Any ideas?
Edit: The flash method I used for TWRM: http://forum.xda-developers.com/showthread.php?t=2449670
Edit2: This seems possibly relevant. When I do "fastboot devices", I get "? fastboot". So something is wonky in terms of its detection. But all the commands seem to be getting executed fine...
Edit3: Finally a potentially useful piece of info: If I flash the boot image extracted from the Cyanogen mod zip, then run "fastboot continue" I get "ERROR: Getting device tree address failed". Which is the same message I get when trying to remotely run a boot image without flashing it. Possibly related to the "?" in the "fastboot devices" listing above? I switched to Koush's Universal Adb Drivers, but no change.
Pretty please?
I find it hard to believe I could manage to brick a 2 week old phone just by following the guides posted here
Well, I still have no clue what went wrong, but I was finally able to make use of the reset to stock thread. It was strange and scary and at no point did I really have any idea I was hitting the right buttons, and at the end it said it failed... BUT it rebooted me into a fresh install, apparently even unrooted! My problems along the way appear to have entirely been related to actually getting the phone *into* download mode since I couldn't get it to actually turn off. Once it ran itself out of battery and turned off, I was able to enter download mode while reconnecting it to power.
No to decide if I want to try installing a custom ROM again, or take this as a sign...
Who am I kidding. *re-roots phone and pulls up the mod threads*
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance!
Looks like you are trying hard to find a solution. I think it may be helpful if you try to manually install the o/s rather that using Wugfresh and report back any errors. See
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ At step 11 I would flash the individual image files and also follow the instructions re erasing and flashing userdata.
AFAIK you will not see an Android device when using Fastboot - Android hasn't loaded at this stage.
Thanks peterk-1. Unfortunately, this does not work. I followed the steps, with the exception of the radio file as my Nexus 10 is wi-fi only. It goes through the stock image update perfectly fine and reboots itself. At that point, it's back to the moving android at the 'erasing' screen.
One thing to note with the link you provided; no where does it indicate flashing a recovery, stock or custom. Now, I've tried flashing stock, TWRP and CWM and none seem to work. TWRP comes closest with the black/blue splash screen, but will not open further.
Any other suggestions would be appreciated.
You did go to the posted link? I quote:
Step 8: We now want to wipe the device. Use the following commands in order:
........
fastboot erase recovery
............
Step 11: We will now flash the system, boot, and recovery ..........................................
fastboot flash recovery recovery.img
Unfortunately, same result...