Related
My gtablet has been very happy and stable with the VEGAn-TAB GingerEdition STABLE RC1 rom for the last couple of months, but I've just run into a problem I can't get out of.
I was connected to my PC via USB about to copy some data off the tablet when everything froze. I needed to cycle power to get back to a workable system. Connected again via USB, and it froze again.
Next I booted into clockwork recovery and figured I'd have a look around to make sure everything was healthy with the filesystem. It wasn't. I was unable to mount the system partition.
At this point, I figured things were looking grim, so I opted to nvflash back to stock and maybe try again with the ROM. nvflash went ok, but after rebooting it bootloops at the white gtablet screen after 10-15 seconds or so.
Now when I try to go into recovery mode, it comes up to a black screen that reads "A N D R O I D", then i get an exclamation point, then it bootloops.
help! not sure how to proceed here.
thanks in advance for any pointers anyone can give me!
Code red (or maybe double red):
http://viewsonic-gtablet-for-dummies.webs.com/
I've gotten clockwork recovery reinstalled using this technique: http://forum.xda-developers.com/showthread.php?t=1058649
From there, I repartitioned the sdcard to 2048/0. It took a lot longer than I remembered it usually taking, but once that completed, I rebooted and got into the stock ROM without further issue.
Thanks for the space -- I've gotten rusty after having not run into any flashing difficulties for a while!
Double red it was! Thanks for that link bmag666. Definitely going in my perma-bookmarks.
Hi everyone, i am using milestone A853 model, i follow exactly the guide to root the phone and everything goes perfect, i can boot up and use all the custom rom as usual. BUT the problem now i having is, it happened randomly sometimes i reboot my phone it just got into this bootloader err 1A,23,35,23,00 and i have to flash the GOT 2.2.1.sbf again and do a nandroid restore, i have to flash my phone around 4 times a week.
FYI, i tried the 3 button combination to get into open recovery but still it leads me to the bootloader err page.. is there anyway i can get rid of this?? i need to constantly be with a pc to get my phone working
[d]amour said:
Hi everyone, i am using milestone A853 model, i follow exactly the guide to root the phone and everything goes perfect, i can boot up and use all the custom rom as usual. BUT the problem now i having is, it happened randomly sometimes i reboot my phone it just got into this bootloader err 1A,23,35,23,00 and i have to flash the GOT 2.2.1.sbf again and do a nandroid backup, i have to flash my phone around 4 times a week.
FYI, i tried the 3 button combination to get into open recovery but still it leads me to the bootloader err page.. is there anyway i can get rid of this?? i need to constantly be with a pc to get my phone working
Click to expand...
Click to collapse
According to this thread, it might be an issue with a bad SD card.
http://www.android-hilfe.de/motorola-milestone/12635-milestone-startet-nicht-mehr.html
Can you try with another SD card?
Is it possibly that you have the older version of the Milestone bootloader? (90.73), you can try to flash the VR from kabaldan's website( http://android.doshaska.net/rootable) instead of G.O.T., you just need to put OR on your SD card yourself.
i am using the bootloader 90.78 and androidiani 3.3 open recovery...i try to format my sd card first see if it helps....i flashed my phone yesterday and using a fresh new iceandfire rom 3.0, i tried a couple of times rebooting and turn off my phone and it just boot up without any problem, however this morning i tried to reboot once more and i got this bootloader error again...frustrating =/
[d]amour said:
i am using the bootloader 90.78 and androidiani 3.3 open recovery...i try to format my sd card first see if it helps....i flashed my phone yesterday and using a fresh new iceandfire rom 3.0, i tried a couple of times rebooting and turn off my phone and it just boot up without any problem, however this morning i tried to reboot once more and i got this bootloader error again...frustrating =/
Click to expand...
Click to collapse
AOR dont updated recently, try FuFu openrecovery. it is based on AOR but have many new features and fix, like mmc fix, ext4 module, etc...
if your problem is beacuse the sdcard then you have the mmc error, what is fixed be kabaldan, and he provided a module for the fix, or you have a broken sdcard.
Changing the a different OR will help? i already apply the dsifix.ko 2.6 by kabaldan in my /system/lib/modules directory, just only did a nandroid restore to my phone now, will monitor how long it will last till the next bootloader err...sigh, btw is it ok if i keep trying to reboot like 5 times in an hour time?
[d]amour said:
Changing the a different OR will help? i already apply the dsifix.ko 2.6 by kabaldan in my /system/lib/modules directory, just only did a nandroid restore to my phone now, will monitor how long it will last till the next bootloader err...sigh, btw is it ok if i keep trying to reboot like 5 times in an hour time?
Click to expand...
Click to collapse
5 times seems a bit excessive to me. If all you are trying to do is see if you will boot into the bootloader when you really wanted the recovery, 2 times every hour or so should suffice.
wait a sec, you can enter the recovery console? try to not use the autoboot to or script. if the phone booted to the bootloader mode you can see a triangle, then push the camera and the volume up button to entering the basic recovery mode.
at this point the sdcard not used. then you can try to the update menu, now the phone trying to load the OR update.zip from the sdcard. if you have problem only with the last step, then your sdcard maybe broken, if you have the error at the first step, it is possible that your phone nand memory is failing. in that case you need to call the motorola customer service for the repair.
vadonka said:
wait a sec, you can enter the recovery console? try to not use the autoboot to or script. if the phone booted to the bootloader mode you can see a triangle, then push the camera and the volume up button to entering the basic recovery mode.
at this point the sdcard not used. then you can try to the update menu, now the phone trying to load the OR update.zip from the sdcard. if you have problem only with the last step, then your sdcard maybe broken, if you have the error at the first step, it is possible that your phone nand memory is failing. in that case you need to call the motorola customer service for the repair.
Click to expand...
Click to collapse
Recovery console? you mean the console mode after enter the androidiani menu?i can go straight into AOR with the camera + power button after turning it off.
whenever i got the bootloader error, i cant do anything though, the camera button with volume up is not working.All i can do is flash the .sbf file again.
But for now my phone is still working since the last nandroid restore i did this morning, reboot a few times normally and also reboot to recovery both are working as usual.
[d]amour said:
Recovery console? you mean the console mode after enter the androidiani menu?i can go straight into AOR with the camera + power button after turning it off.
whenever i got the bootloader error, i cant do anything though, the camera button with volume up is not working.All i can do is flash the .sbf file again.
But for now my phone is still working since the last nandroid restore i did this morning, reboot a few times normally and also reboot to recovery both are working as usual.
Click to expand...
Click to collapse
it is sadly, but it is possible that your phone nand memory unstable or have some crc error. do you often reflash before?
vadonka said:
it is sadly, but it is possible that your phone nand memory unstable or have some crc error. do you often reflash before?
Click to expand...
Click to collapse
i only started flashing few weeks ago but the bootloader error occur too frequently that i have to flash at least once every 2 days...for now i see that it lasted longer than usual,if it is really nand memory unstable means that there is nothing i can do to fix it?
[d]amour said:
i only started flashing few weeks ago but the bootloader error occur too frequently that i have to flash at least once every 2 days...for now i see that it lasted longer than usual,if it is really nand memory unstable means that there is nothing i can do to fix it?
Click to expand...
Click to collapse
you cant fix that, only the motorola service, but i suggest to try it some benchmark software like antutu benchmark. with that you can test the memory and see what happened.
well i guess the only solution will be not turning off my phone/reboot for as long as i could, don't wan to take risk later it gets into bootloader error again
My phone always stuck at bootloader when it's hot while booting up.
Wait few minutes or use a fan to cool it down will solve it.
When this happen, recovery mode won't start
and flashing new ROM won't help or even make problem worse because of extra heat produced.
Avoid rebooting after gaming/heavy use is my workaround.
imTigger said:
My phone always stuck at bootloader when it's hot while booting up.
Wait few minutes or use a fan to cool it down will solve it.
When this happen, recovery mode won't start
and flashing new ROM won't help or even make problem worse because of extra heat produced.
Avoid rebooting after gaming/heavy use is my workaround.
Click to expand...
Click to collapse
when u stuck in the bootloader it shows the error code like mine? or just the usual bootloader screen? i tried leaving the phone for few hours without doing anything but it still stuck at the bootloader screen with error code =/
I doubt this will help, but can you try flashing an official 2.2 sbf and try it for a few days? or maybe get an official 2.2 sbf, then root it, then install a rom.
hey there just to informed you guys here that my phone currently had no bootloader error so far for a week, i am using Froyo Mod 2.9.3 and everything just work well. Wonder what happen actually to my phone previously when i flash other rom.
Just wanna ask will the following step i did causes a bootloader error?
-Flash 2.2.1 got sbf files.
-Reboot to recovery (using the latest minimod), Click on root phone (i not sure will this cause the problem as this is suppose to be for stock rom?? plz correct me if am wrong)
-Wipe Dalvik,cache and data
-Apply update of custom rom and gapps.
-Reboot
Hey Guys,
So I have been all threw the forum over the past week plus trying to find a solutions and have tried the majority of the ones on the site. Here is what happend:
HOW I GOT HERE:
I was running a CM10 nightly build from 01/15/2013 that was installed via CWM. I had been running it for about a week. When I went to bed I set my phone on the nightstand. About 2 hours into sleep the phone rebooted as I eventually woke up and noticed it thinking it was just the phone wonking out. When I up fully 6 hours later the phone was still rebooting. Since then when ever I cut on the phone it will no get passed the Google logo with the padlock. I can boot into fastboot and recovery. I am running the latest CWM 6.0.2.5.
PHONE VITALS QUICK GLANCE
Android ROM version: CM10 01/15/2013 Nightly Build
Baseband: D720SPRLC1
Bootloader: D720SPRKC5
Recovery: CWM v6.0.2.5
WHAT I HAVE TRIED
Restoring from backup
My first fix was to flash three different roms via recovery (doing full wipes each time)
Then I tried flashing a new recovery
Formatting /system, /cache, /data, and /boot and then flashing a new rom
Then I focused on trying to get the USB storage to mount so I tried using adb shell to repair the file system and that worked
Then I tried new roms and things got REALLY weird. When I would place a rom on “sdcard” it would be available to flash. When I flashed it though it would not take and upon returning to recovery it wouldn’t be there or when I mounted the storage again. After about 10 times of this I figured let me make sure I am not crazy and try the following.
Format the internal storage. In windows when I tried this windows would show that the device formatted and was empty one I dismounted after putting items on it and go back to storage by both remounting it or by recovery the old data would come right back. In Ubuntu when I tried formatting it both via disc recovery and gparted they both said the device was empty but that they were unable to create a partition.
So then I went down the path of all of the debricking tools out there including the one from AdamOutler's (I think it is called ressurector), ODIN, and the Nexus Root Tool all with varying results.
Ressurector kept saying injection failed
ODIN just does not work on the nexus s from what I can tell (spent a day researching and no one seems to give a definitive answer on this one)
And Nexus Root Tool attempts to flash back to stock but runs into an error with the baseband.
So next I decided to try and flash back to stock using the Google images. Using Ubuntu I ran the flash-all.sh that comes in the zip and kept running into the baseband issue.
So next I found OldBlue910’s post with all the OTA updates and I went after trying to use that to fix my phone. Thanks to the amount of instruction he gives I got a lot further and got the flash-all.sh in his stock zip to give me a better error message telling me which baseband I needed to have to go back to stock which when I double checked he includes in the zip. The problem is when I try to flash that radio fastboot tells me I was successful but the bootloader still reads as D720SPRLC1 and does not change regardless of what I do. When I try flashing the stock images again after flashing the radio I receive the same errors.
So now I think I have hit the real brick wall and unless someone has any advice I will need to go and buy a new phone. Hoping you guys can help. I figured if you guys can figure out a hard brick then this is still doable, I have just exhausted my own realm of knowledge.
Please and thank you’s to anyone with advice.
Could you get any lights ON? The buttons or the screen?
lights are on
Yes during the boot loop the Google logo comes up, then the screen goes black, then the Google logo comes back, and finally in about 20 seconds the lights come on. Once that happens after about 4 minutes the process starts all over again.
Hello everybody here at XDA, ( this is my first post here so bare with me here)(english is not my native language either)
My device:
Nexus 5 - hammerhead D821(H) 16GB
BL version - HHZ12h
BB version M8974A-2.0.50.2.26
Secure boot enabled
lock state unlocked
today i got a "broken" nexus 5 that is in boot loop with the google logo and it wont boot into any .img
At the start i read the pinned posts and found this tutorial: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
followed it step by step. but unfortunatly it didnt help my situation. there werent any errors or such kind.
i also tried this tutorial with other images but nothing worked.
When i go to the recovery mode and press the power button the phone get into the google logo and i can see some sort of strange stripes in like a milisecond but then it just gets into the boot loop.
i really think ive tried everything accept for relocking the bootloader but cant imaging that this could be the problem.
If you guys need more info please just ask me.
Hope you guys can help me out here.
Martin
Really thought XDA forums would be able to help me.
Any admins or mods or any other veteran that could help me out?
If that's not working for you, you can try using the Nexus Root Toolkit just to be sure.
If that doesn't work, than it could be hardware related, and not much you can do about that.
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
mesh120673 said:
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
Click to expand...
Click to collapse
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
spookytay said:
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
Click to expand...
Click to collapse
It says Locked.
I unlock it using ./fastboot oem unlock
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Nurmi_CEO said:
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Click to expand...
Click to collapse
Yes the bootloader must be unlocked before you can do ANYTHING to the phone, it's what's there to protect it from being hacked/changed or whatever. So before you can write anything to your phone, you need to make sure you OEM UNLOCK the bootloader.
[Solved!] Nexus 5 boot loop at Google logo
I found a solution on Youtube comment (can't post url, too new user).
You just have to press quickly the Power button durint 1-2 minutes (continue untill the Android animation start, don't stop when the Google logo appear)3
As crazy as it sounds, IT WORKS
Wow .. i had the exact same problem (Startup loop on Nexus 5 that shows the Google logo and restarts, over and over), and i pressed the power button quicky about 30 or 40 time until after I saw the startup animation and my phone came back to life. I have been charging it with cables other than the one that came with the phone for a few months now, and it has been acting strangely while plugged in (randomly clicking things on the screen, and enabling my camera and taking pictures on its own, etc.). So, to avoid problems in the future, I think I'll invest in a wireless charger. Thanks JackNUMBER for the easy solution. I hope this works for others as well. Saved me a trip to the store.
Hello, I'm about to giving up,
Something happened to the phone and now it won't boot, it barely show the "ANDROID" logo when it restart itself. I can enter to the recovery menu, it doesn't have clockwork recovery nor twrp, just the basic recovery. So far I tried:
wipe data/factory - didn't work.
wipe cache partition - didn't work
apply update from adb: Adb just work with sideload and that's it, for everything else it shows closed. I tried sending the rom with sideload and it fails every time:
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
So I took my sdcard and copied the room there, so I tried
apply update from sdcard, it starts and in no time it says:
Installation aborted (APPLY_EXT).
I'm very frustrated right now, nothing works, it seems that the manufacturer did great effort on being the only one who can recover this phone, who appears to be from China, the MTK6582.
Fastboot? it doesn't show the device, it would be my last hope but no, since there is no adb, I cannot call fastboot, and the apply update from adb only work with sideload (yeah, f**k me).
The best course of action would be to throw it to the trash?
Thanks!
Hey, I'm in a similar position to you. However, I went about it with a slightly different route. The chip used in this phone is the MediaTek 6582 (I think?). I downloaded some tools from a thread on here that includes the 320 rom and the necessary software for flashing. I've flashed MediaTek devices before, the Huawei Ascend G610 and G700, both successfully. This one is giving me headaches, the damn device keeps disconnecting. HOWEVER, if you're lucky and you don't have the same problem with disconnecting hardware, you should be able to flash a new rom via the software. It'll take a while though. Also, I don't know what'll happen to your IMEI afterwards, so that's another possible headache (both the G610 and the G700 lost their IMEI info, but I'd taken steps to back them up beforehand so I could just restore them; here, there's no option to backup).
Here's the thread: http://forum.xda-developers.com/android/general/htc-mtk-cpu-flash-files-flashtool-t3114271
Let me know if you need help. I'm screwed in that the damn phone keeps disconnecting. Similar to you, no fastboot either. Plus, no RUU for this HTC. Hell, the internet barely knows this flipping phone.
Cheers, and good luck.
blitz9826
0Camus0 said:
Hello, I'm about to giving up,
Something happened to the phone and now it won't boot, it barely show the "ANDROID" logo when it restart itself. I can enter to the recovery menu, it doesn't have clockwork recovery nor twrp, just the basic recovery. So far I tried:
wipe data/factory - didn't work.
wipe cache partition - didn't work
apply update from adb: Adb just work with sideload and that's it, for everything else it shows closed. I tried sending the rom with sideload and it fails every time:
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
So I took my sdcard and copied the room there, so I tried
apply update from sdcard, it starts and in no time it says:
Installation aborted (APPLY_EXT).
I'm very frustrated right now, nothing works, it seems that the manufacturer did great effort on being the only one who can recover this phone, who appears to be from China, the MTK6582.
Fastboot? it doesn't show the device, it would be my last hope but no, since there is no adb, I cannot call fastboot, and the apply update from adb only work with sideload (yeah, f**k me).
The best course of action would be to throw it to the trash?
Thanks!
Click to expand...
Click to collapse
Ditto!!!
Hey guys I am having the exact same issue, luckily for me it is my Mrs who done her phone in and not mine . She has the HTC Desire 320, I believe she tried to root it on her own without even asking for advice, I think she used the app Kingo Root, she said she went to remove the root but when she uninstalled the app it didn't remove it. (LOL I told her well perhaps that's because there will be some way of removing it, aside from just uninstalling the app), anyway she proceeded not to care and carried on using her phone as normal for maybe a week or two at most, then about midnight one night, came down and said to me,
"my phone had an update and on restarting I just get a dead android, if you press the power button you get some options so I clicked erase"
Click to expand...
Click to collapse
I was like nice so basically you F***ed it!!!!, and for about 2 weeks now I have been endlessly reading post after post, forum after forum, trying rom after rom, RUU, all kinds of things.
Here is the situation, the phone will boot as far as the HTC logo, it will get stuck in a short loop and reset itself 4/5 times repeating the HTC logo, eventually it will end up at the dead android pic (the android on his back with the red exclaimation mark triangle) with the words 'no command'. From here I can press the power button once to get a list/menu of items (What I assume to be the recovery menu). I can backup data, I can restore the backed up data (both of which do nothing as I guess there is nothing really to back up), There is an option to restore from sd card (which I have tried numerous roms and to no avail have any been successful), I can erase the cache and I can also erase everything and recover, the erase side works fine, I did notice in each of these menu that if you press volume up to activate them and then press the power button once, then the writing dissapears and the android proceeds to have his moving atom type thing in his belly, saying 'erasing..', however even with them completed successfully, it still does not restore.
NOTE!!! If you choose the erase and restore method, once activated with volume up, press the power button to get the spinning atom and erasing... message, when this finishes the phone will reboot, it goes to the htc logo, resets itself, goes to the logo again and then just stays at a black screen (almost like a frozen state, I left it for quite some time and it never changed).
I should also note, which I didn't to begin with, but no matter how long I hold the volume down and power button, there is no such hboot/fast boot menu at all, if you hold the volume down and power button even after it displays the htc logo, the phone just proceeds to endlessly reset and loop through the same process forever.
The only thing I can seem to access with little success, is the ADB CMD prompt through the Android SDK,
Code:
adb devices
will indeed return the device (a set of numbers with the word sideload beside it)
Code:
adb usb
Apart from the odd fluke, this has seemed to fail everytime with either an error about a protocol or an error stating 'closed'
Code:
adb sideload "ROM_FILENAME.ZIP OR .IMG
Occasionally this will throw the protocol error, but generally succeeds and displays the 100% most of the time, however the phone doesn't even try, it just almost instantaniously returns the error message :
Code:
[B][I]Installation Aborted (APPLY_ADB_SIDELOAD)[/I][/B]
NOTE!!! That the android lays on his back with this error, but it only says error below not no command.
I am pretty sure that I already came across a solution very similar to the one you posted above, and I just couldn't get it to recognise the phone, the only way the RUU would work, was by completely removing the battery and plugging in the usb, however without the battery in the phone, it just constantly beeps via usb, so I guess it turns on, then off, then on, then off, forever!!! So the RUU fails everytime, if I leave the battery in and try, the RUU program does nothing whatsoever! So I am at a complete loss with it now.
Cheers
GunnerJnr
Any luck with unbriking the HTC?
Maybe this is the solution, good luck.
Search: How to Unbrick every MTK China Phone ! Preloader / SP Flashtool Fix [HD] on Youtube
Responds please.
http://forum.xda-developers.com/showpost.php?p=64659997&postcount=16
I think that you no tell true because I tried this method with volume keys and nothing. Flash tool still show error. Its impossible to write android without battery. I think really put your phone to rubbish or sell as lcd+digitizer parts I think just we must waiting for new custom rom flashable via stock recovery. 320 is still new model and developers no moke any custom rom. So maybe only HTC service may help, only in HTC Factory peoples know how install android and bootloader on hard bricked device.