Hi,
I tried to revert to stock rom on my PQi WiFi only adam today from EdenX. But when I started the procedure (as explained in the stickied thread on this forum), the unbricking seemed to stop when trying to transfer the system.img file (it's stuck at 67502080/134948352 bytes for over half an hour now).
What can I do to fix this? I'm sort of reluctant to simply shut my adam down, since I've read that that can perma-brick it. Any advice on what to do?
thx
EDIT: nvm, it sort of settled itself. The terminal simply shut down without my noticing, so I tried to run the unbricking software again and it simply worked like it should, I'm not seeing any problems with it... very strange, but it works again
Start the procedure from scratch - you don't need to go out the forced usb mode.
After all what I have experienced it will not permabrick your adam (as long as the boot image is there - alse the complete wipe you id was NOT complete as intended - so nothing bad will happen)
Related
I was trying to tether my new Hero to a linux host (unsuccessfully) and followed what I thought was a good "how-to". I installed a recovery image and I think could be causing my phone to lock-up on a daily basis. Is there any way to remove it or reset the phone COMPLETELY back to factory? If not, I understand I need to live with what I've done, but if there is, could anyone point me to the proper procedure?
Thanks in advance!
MadOtis said:
I was trying to tether my new Hero to a linux host (unsuccessfully) and followed what I thought was a good "how-to". I installed a recovery image and I think could be causing my phone to lock-up on a daily basis. Is there any way to remove it or reset the phone COMPLETELY back to factory? If not, I understand I need to live with what I've done, but if there is, could anyone point me to the proper procedure?
Thanks in advance!
Click to expand...
Click to collapse
Yes this is possible, you need to download the Sprint 1.29 ruu, connect your phone via usb cable and execute it, it will fully reset your entire phone. Unless you messed something up installing the recovery (difficult but not impossible to do) it shouldn't be causing you any grief. Going back to bone stock and giving it one more shot, paying careful attention to follow the steps verbatim might not be a bad idea either.
I don't see what other app I've installed could be causing it to lock up. The only one that's fairly "iffy" is the Slacker android app, and it's easily killed from process viewer and restarted (and all is well again). But, I've been having just about daily lock-ups since following the how-to.
I'll go find the Spring 1.29 ruu and go from there a little more carefully.
Thank you!
Today, I upgraded my Legend to CM7 Nightly 32 (from Blayo 0.7 with a full wipe). Prior to that, I made a nandroid-backup in order to be able to go back, in case something went wrong. Well, something did go terribly wrong:
I now have frequent bootloops right after the HTC-logo. If I try it a couple of times, it eventually boots as if nothing were wrong. The system seems stable and works smoothly. The only obvious problem is, that android isn't recognizing my sdcard. That's why, I decided to roll back to Blayo. Unfortunately, that isn't possible, because my PC doesn't recognize my phone anymore. I therefore am not able start the recovery mode...
Let me summarise the situation:
* The phone doesn't recognize ANY sdcards. I went to the store to buy a new one, but that didn't change a thing. The sdcard that was in the phone, when I performed the upgrade, seems completely dead. The pc doesn't even recognize it, if I put it into a card reader. After I put the new one into the phone, it started behaving kind of strangely in my pc as well, although that could be the usb-sd-adapter. Or do you think that the phone could have suddently started frying sdcards?
* My PC doesn't recognize the phone any more. That's why, I cannot boot into recovery mode and hence cannot install any other rom.
I am really desperate here and would appreciate it, if any of you guys could help me in my predicament...
Regards,
Nikolas
I'm fairly sure you are USB bricked. Search the forums on how to fix it, also to avoid this problem, use fake-flash from the ROM Manager application on the Android Market.
You most likely brick'd your phone. Follow this guide to get it back up. Dont worry, i have brick'd my phone more then ones, and always gott it back up
Thanks to your valuable advice, I got everything working again!!!
The first step in the tutorial actually fixed my sdcard problems, which made the rest a hell of a lot easier. After having sd-capability back, I followed marclh1992's hint concerning fake-flash and was thus able to install RC4 without having to use a PC. I still had the problem of bootloops though. Since the phone started normally, when connected to a power source via usb, I reckoned that this behaviour must have still been due to the usb-brick. That's why, I followed the tutorial through to the end. After that no more loops, no more sdcard problems - just perfect!
Yours thankfully,
Nikolas
I have looked high and low for a similar thread (detailing my specific problem) so I apologize if it exists and I was unable to locate it. I attempted to flash the PRIMEE ROM on my Acer with all apparently going well until the end. Messages were displayed saying that data, cache, etc. could not mount or something to that effect. I foolishly rebooted only to find that the Iconia will only display "Unrecoverable Bootloader Error (0x000000004)"
That's it. It is completely unresponsive to any other attempts to factory reset. Power/volume does nothing. I have looked extensively for some solution to this problem (attempted Reset button, moving lock screen slider/power-volume combination). You name it, I've tried it. It was briefly recognized by my PC when connected via USB but the AXP drivers were not found and did not install. I'm really flummoxed here.
Again, apologies if this is a duplicate thread but it seems fairly unique in that I cannot get any response at all. I fear that I've really done it this time. Any help would be greatly appreciated.
You DID install the custom clockworkmod app from the dev section, right? Not the one from the market...
Clockwork.....
No, unfortunately I did not. Didn't even realize there was a difference. I did install the Acer Recovery App as well, but otherwise, I think I'm pretty well screwed....
Well mate,now thats a huge problem you got there. If you would've screwed the /system partition np, /data partition,also np.....But uhh,bootloader error...i got the feeling your flashing has screwed up the internal Kernel of the Device,which is connected to the Bootloader,and without a Bootloader...well as its name says,you cant boot anything. Its like a Bios to a normal Computer,if you screw up the Bios,basically you can throw your Motherboard away...and sadly,the tablet comes all together,also i dont think Acer's Warranty will do anything about it aswell since you flashed an unofficial ROM/Kernel.
Your only solution is to send it to Acer,and see if your lucky enough and they fix it for free,if not ...well pay or get another one.
Goodluck with your problem mate.
Respect.
Yeah - kinda figured as much. Very disappointed that I lost it but I suppose I can make one last ditch effort to get it to Acer and see if they'll replace it but I'm skeptical at this point. Oh well - first time for everything. Lesson learned. Thanks for the help all the same.
First, congratulations. You managed to get the unrecoverable bootloader error
--> PM me with your UID, I may help you.
..............Edited..............
You should talk with sc2k I was in the same position you're in with the Unrecoverable Bootloader Error. Sent sc2k the UID for my A500 and he was able get my A500 back up and running again.
first of all, make sure you have a sd-card.
second. dl a stock rom to your PC 1.10.42 for instance, extract with decrypter and put the update.zip on the sd-card using a card reader or maybe your phone.
the put the sd-card back on your ICONIA.
after do the following:
hit VOLUME + (volume up) and power, until it vibrates, keep you finger on volume + and toggle the screen toggle switch.
it will then say formating data and formating cache, and the will start to flash the update.zip
once finished you should be ok.
Hi,
i have the same probplem, can anyone help me?
i have installed a custom firmware from thor and enabled the 3g option, my a500 will only vibrate after reboot with the error "Unrecoverable Bootloader Error (0x000000004)"
i cant read out the UID or anything else ... can anyone help me???
APX Mode runs but i cant recover with nvflash ...
I included this in another thread but thought it might help more if it had its own thread.
Problem:
SVF:105:1:2
Failed to boot 0x1000
SOLUTION:
Download: http://dl.dropbox.com/u/23255832/Atrix Unlock/AUTOMATIC_UNLOCK_V4.2.zip
Download the program
- Once unzipped in a folder open the file MAIN
- Do the repair first (option 3)
- It gives you instructions as you go
- Then I did option 1, follow instructions and chose 2.3.4
- Phone is alive again
- Then I did option 3 and followed instructions.
Thats it, easy.
What a waste of a day. Do the repair first, then reload and you're good to go.
I just noticed the link doesn't work. It was an automatic root/cwm dos program that had a menu if anyone knows what I am talking about. I just cleaned up my pc and can't seem to find it either. Will keep looking for it.
Found it!
http://forum.xda-developers.com/showthread.php?p=24472332#post24472332
Its labeled AUTOMATIC_UNLOCK_V4.2
jjj133 said:
I just noticed the link doesn't work. It was an automatic root/cwm dos program that had a menu if anyone knows what I am talking about. I just cleaned up my pc and can't seem to find it either. Will keep looking for it.
Click to expand...
Click to collapse
Here it is, from the link you posted on the other thread (found it through the list of your posts):
http://forum.xda-developers.com/showthread.php?t=1182871
A few problems:
This tool already has it's own thread. And it is already known that this tool fixes failed to boot errors (I mean, it is Option 3).
You should not post the thing in multiple threads.
This post does not belong in the dev section.
Edit:
Forgot to mention that I am glad you got your phone working again.
My Phone is showing following message:
SVF:105:1:2
Failed to boot 0x1000
NVFlash...
Nothing more, and it is actually shutting down after few moments automatically.
Any hope? I had this issue long time ago, and it is still there.
yeah same here 0x1000 and it reboots so can't i fix this? I try holding down the volume down and it restarts any help?
has anybody tried on bell atrix?
thks
This is softbrich. Hardbrick not fix.
Sorry guys, meant soft brick but I couldn't change the title after I wrote it. I just wanted to put it up because when I bricked mine it took me like 7 hours to find all of the info on how to do this. Maybe is better documented now (this happened months ago to me). Still, I wanted to post to help others. Hope it helps
Tl;dr: I(dumbass) bricked my phone to the point, where I only can get the bootloader. No fastboot mode, no recovery, no boot.
How: I rooted my phone to a pretty good working state of stock OS+Magisk, right after I got it (Android 10). Later after a couple systemupdates and the patch to A11 and even more updates I thought, it would be time to patch magisk again, or revert to unroot, so I tried patching magisk, but somehow my phone got a lot of bugs, like no sound and very long boot times.
Then I tried reverting back by adding a stock boot image and stuff and a lot of things went unlike any tutorial said and now I'm stuck on beforementioned phonestate.
My PC(Asus Notebook) with installed Qualcomm-Drivers and Oneplus-drivers only recognizes the phone when I try to connect it via EDL-mode (vol-up+down+connect USB) but only for like 10 sec. Then bootloader starts up annd connection is lost.
What would be the most logical approach? How do I start?
And yes, I read a lot of posts trying to fix it myself, but I can only find so much.
This will work. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
MRobbo80 said:
This will work. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
Click to expand...
Click to collapse
Are you using the correct cable?
Thread can be closed.
I followed the beforementioned link already but on my homepc I had some issues with the tool and/or drivers, I think.
Now on my notebook Ijust wasn't quick enough, so the phone restartet into bootloader after a couple seconds.
After a couple tries it worked.
Whew, glad that worked out. I bricked my Optimus M and this guy Asdullah took time out of his day to video chat with me and help me unbrick my phone. Some folks in this community are ****ing awesome!