Soo….Go ahead and call me a noob, laugh at me, do whatever it is that you want to do to me…but…..
So there I was following Justin Case’s instructions to a T trying to avoid bricking my phone and pow I finished everything, finished the second to last step I should say.
I stopped the script in the second to last step, and my dumb self got distracted and didn’t complete the last step, I unplugged my device and restarted it without completing the step:
Code:
adb shell mv /data/DxDrm /data/DxDrm_trash
adb shell dd if=/sdcard/CIDBLOCK.img of=/dev/block/mmcblk0p5
adb reboot
And, now I am pretty sure that my phone Is bricked, sooooo…… Is there any way to fix it, or am I out 600$ and buying another one?
BigRed35m said:
Soo….Go ahead and call me a noob, laugh at me, do whatever it is that you want to do to me…but…..
So there I was following Justin Case’s instructions to a T trying to avoid bricking my phone and pow I finished everything, finished the second to last step I should say.
I stopped the script in the second to last step, and my dumb self got distracted and didn’t complete the last step, I unplugged my device and restarted it without completing the step:
Code:
adb shell mv /data/DxDrm /data/DxDrm_trash
adb shell dd if=/sdcard/CIDBLOCK.img of=/dev/block/mmcblk0p5
adb reboot
And, now I am pretty sure that my phone Is bricked, sooooo…… Is there any way to fix it, or am I out 600$ and buying another one?
Click to expand...
Click to collapse
Send a PM to Jcase; looks like he is being very helpful in this regard. Good luck!
The DNA will have 2 appointments, first with a microwave and the second with Verizon return department.
BigRed35m said:
And, now I am pretty sure that my phone Is bricked, sooooo…… Is there any way to fix it, or am I out 600$ and buying another one?
Click to expand...
Click to collapse
I was wondering... I bought my phone at retail and activated on my line to keep unlimited data. I'm also paying for insurance through Asurion. Since I bought it at retail, the insurance will should still cover it correct? You could use your warranty or insurance ... you have 14 days through verizon lol
ilogik said:
The DNA will have 2 appointments, first with a microwave and the second with Verizon return department.
Click to expand...
Click to collapse
LOL....OUCH.....Yeah...the 2 second Microwave rule....
BigRed35m said:
Soo….Go ahead and call me a noob, laugh at me, do whatever it is that you want to do to me…but…..
So there I was following Justin Case’s instructions to a T trying to avoid bricking my phone and pow I finished everything, finished the second to last step I should say.
I stopped the script in the second to last step, and my dumb self got distracted and didn’t complete the last step, I unplugged my device and restarted it without completing the step:
Code:
adb shell mv /data/DxDrm /data/DxDrm_trash
adb shell dd if=/sdcard/CIDBLOCK.img of=/dev/block/mmcblk0p5
adb reboot
And, now I am pretty sure that my phone Is bricked, sooooo…… Is there any way to fix it, or am I out 600$ and buying another one?
Click to expand...
Click to collapse
Did you get any help on this? Did you try jcase on the IRC.
I didn't figure out if it was fixable, I ended up taking it back and they were understanding and just gave me a new one.
BigRed35m said:
Soo….Go ahead and call me a noob, laugh at me, do whatever it is that you want to do to me…but…..
So there I was following Justin Case’s instructions to a T trying to avoid bricking my phone and pow I finished everything, finished the second to last step I should say.
I stopped the script in the second to last step, and my dumb self got distracted and didn’t complete the last step, I unplugged my device and restarted it without completing the step:
Code:
adb shell mv /data/DxDrm /data/DxDrm_trash
adb shell dd if=/sdcard/CIDBLOCK.img of=/dev/block/mmcblk0p5
adb reboot
And, now I am pretty sure that my phone Is bricked, sooooo…… Is there any way to fix it, or am I out 600$ and buying another one?
Click to expand...
Click to collapse
Here you go : http://rootzwiki.com/topic/36898-stock-return-to-stock-1156054-for-verizon-htc-dna/
Related
Hi, I'm trying to help a fellow Atrix user after he formatted and partitioned the internal flash memory using Tenfar's CMW Recovery.
He has lost touch on the bottom part of his screen; about a 1/2" of screen space doesn't work.
Tenfar posted that he had done this too, and had resolved this by reformatting with the Stock Recovery. Another user asked in that same thread how he accomplished that, but no answer has been given yet.
This user cannot get the Recovery Menu to show up because of the lower touch screen not working.
Can the steps be run blindly without the Recovery Menu showing up?
Or, can someone help me on how to have him format the internal memory via ADB?
I've had him try the following ADB commands from both the /!\ Recovery Screen and after enabling Early USB Enumeration without luck.
Code:
adb shell
$ su
# format DATA:
Comes back with format: not found.
Can anyone help? I've seen a few others with this issue but have yet to see a full solution posted for those that aren't ADB experts.
I have this problem too! Tenfar was kind enough to try helping me but apparently I'm a retard and unfortunately can't follow his instructions. I've been spending an entire week reading hours each day and I'm embarrassed that I still can't fix it, despite him sending me almost a dozen PM's trying to do so. Very grateful but sad that I'm so dumb.
He's told me to do this:
$adb shell
$su
#busybox umount /sdcard (hit enter key)
#newfs_msdos -F 32 -S 512 -L MB860 -c 64 -u 16 /dev/block/mmcblk0p18 (hit enter key)
I'm not sure where to do this. I now think I do this while the device is in Early USB Numeration but I haven't tried it yet. The wife was getting really pissed because I spent the entire weekend trying to fix this and have been investing too much time on the computer. She's... having mad PMS so I'm leaving it for a few days lol
I tried earlier when the phone was booted up but after some research, believe it may need to be done in Early USB Numeration mode but there's only about a minute before it automatically reboots. I haven't tried this and hope that my assumption is correct. I know about 3 other people who are currently experiencing this challenge and I hope that it corrects it.
The wife is working a double shift today so I'll try after work. Can't blame her for getting upset with me. Soft bricked a few other phones but fixed them with relative ease. This has been by far the toughest. It was my birthday last week and I spent most of my day on the computer trying to fix my Atrix lol
After this, no more formatting internal SD partitions!!! Paypal is giving me grief but I plan on giving Tenfar a modest donation. He's been very supportive of my dumb ass lol
In this forum there is a very good guide on how to use adb. Can't remember where exactly it's at I just did a general search for How to use adb it may help you.
Edit I think this is the link androidsamurai.com/forum/viewforum.php?f=12
coldfusionb said:
In this forum there is a very good guide on how to use adb. Can't remember where exactly it's at I just did a general search for How to use adb it may help you.
Edit I think this is the link androidsamurai.com/forum/viewforum.php?f=12
Click to expand...
Click to collapse
Thank you!
I managed to install Ubuntu and I really like that.. tried from there too and it wasn't working. So I think it's definitely a problem with my dumb ass. If and when I get it working (I'm determined!...... and sort of stuck lol) then I'll post a guide.
Fuuuuuuuuuuck!!! Still not working!!
Yeah.. i ended up wiping with stock recovery and still a no go. Still no lower half of the screen or buttons. Sucks big time
Once ADB can be run in the recovery menu I think it should be fine.
Tenfar said he's fixed this problem but I'm no sure where he's run these commands. I feel bad after sending him a ton of PMs so I'm just waiting until he updates his Recovery app.
You could try restoring your sbf in rsd
Sent from my MB860 using XDA App
sgtmedeiros said:
You could try restoring your sbf in rsd
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
That's been mentioned and tried multiple times.
I have a simple script written with the command lines from Tenfar, but I am getting his input via PM to make sure it's correct and when exactly to run it. Hopefully he'll be able to direct me on how to get it done. Unfortunately, even if he says it looks right it's going to be completely untested. :-/
Sent via rooted Moto Atrix using Tapatalk
das8nt said:
I have a simple script written with the command lines from Tenfar, but I am getting his input via PM to make sure it's correct and when exactly to run it. Hopefully he'll be able to direct me on how to get it done. Unfortunately, even if he says it looks right it's going to be completely untested. :-/
Sent via rooted Moto Atrix using Tapatalk
Click to expand...
Click to collapse
There's still a glimmer of hope, buddy. Once we get ADB access in Recovery I think all should be well.. unless partitioning this block somehow corrupts and kills the digitizer or something.
I actually couldn't wait any longer. Ported to Bell and got a new Atrix so if things go bad I'll have an easier time swapping. When I fix this AT&T one I'll sell it to pay off my cancellation fee with Rogers. Or, if I end up sending it to Motorola I can go back with my buyer's remorse period and go back to Rogers.
Hope you've got a backup phone or something to use in the meanwhile, man. This issue drove me INSANE!!
Hope is good, but this isn't necessarily for me. That's why I can't test it; this didn't happen to my phone. I have just been trying to help those who this did happen to. I'm also sure it will continue to happen if the CWM port for our phones isn't preset to format correctly.
Glad you were able to get a working phone again, but too bad a phone had to go back under these conditions.
Well, I'll keep trying to figure it out; waiting on another reply from Tenfar. Our schedules don't mesh too well, so if there's anyone else that might have experience in formating via ADB any help would be appreciated. Thanks!
Sent via rooted Moto Atrix using Tapatalk
I have the same problem, I just wanna know if anyone found a solution to fix that?
Also, I live in Belgium (Europe), I bought the atrix in usa a month ago during my honey moon. Motorola Europe doesn't support yet the atrix, I don't know what to do!
The phone is not usable anymore, like someone said: "clicking on the soft button area registers as a click on the bottom of the screen". So, the back button don't work anymore (you have to reboot when your stuck in a menu!)
hi guys i'm currently with a reflashed stock 1.83 rom, i can use android recovery (there the bottom screen portion works) and i can run wipe data/cache.
but no matter how many times i tried when the phone finally boots up it starts with motoblur setup and i cannot pass it, all the buttons work like the bottom of the visible screen and i cannot raise up the keyboard to turn the setup off...
i read in the sbf thread that would be possible to flash or not some particular areas, so if the problems is the wrong partitioning of the /dev/block/mmcblk0p18
maybe some of them could create a sbf replacement toreflash only that partition
other side i was talking with bongd and he says he had problem with the psd.bin file that is in the mmcblk0p03...
so what is the current status of this? adb seems not to work even in early enumeration usb mode...
what if we execute the script using the update.zip function?
i can access my sdcard from windows in storage mode
if we put the script in one signed update.zip into the sd the phone should be able to execute itself?
KeRmiT80 said:
hi guys i'm currently with a reflashed stock 1.83 rom, i can use android recovery (there the bottom screen portion works) and i can run wipe data/cache.
but no matter how many times i tried when the phone finally boots up it starts with motoblur setup and i cannot pass it, all the buttons work like the bottom of the visible screen and i cannot raise up the keyboard to turn the setup off...
i read in the sbf thread that would be possible to flash or not some particular areas, so if the problems is the wrong partitioning of the /dev/block/mmcblk0p18
maybe some of them could create a sbf replacement toreflash only that partition
other side i was talking with bongd and he says he had problem with the psd.bin file that is in the mmcblk0p03...
so what is the current status of this? adb seems not to work even in early enumeration usb mode...
Click to expand...
Click to collapse
Tenfar told me it was mmcblk0p18 but it's actually mmcblk0p03 which needs to be corrected.
There's no ADB in recovery right now. Tenfar's apparently got it working but hasn't released it yet.
I also guarantee you can bypass the Motoblur setup as well. Hit these keys:
?123
ALT
ABC
e
?123
ALT
ABC
e
b
l
u
r
o
f
f
I'm positive because I've literally flashed every SBF and I've spent a lot of time troubleshooting this issue.
really i cannot open the keyboard while i'm in the blursetup screen, i keep pressing the menu button but it highlights only the emergency call and after many seconds it chance to emergency call screen...
At this time, your phone is 'bricked' since we can't get ADB access.
Sent from my MB860 using XDA Premium App
we don't have adb access but i tried and we can use the update function in the stock recovery...i tried to put a update.zip of my old milestone and the process worked till the sign verification that failed.
in the milestone that update.zip is used to run the updaterscript that launches the openrecovery by skrilax_cz, that works like the recovery of tenfar
i guess that if we have a correct update.zip for atrix and we put in it the script we need, it should be run.
unfortunately i don't have the knowledge to build the correct script and don't have access to a signed update.zip for atrix.
if we only could gain some interest of the devs i think our problem could be solved in short time...
edit: i sent 2 pm to tenfar but did not reply, maybe someone has more luck...
looking 100% safe unlock method via efs for galaxy europa and yas used boards but has anyone unlocked one recently without bricking phone
serialkillazzs said:
looking 100% safe unlock method via efs for galaxy europa and yas used boards but has anyone unlocked one recently without bricking phone
Click to expand...
Click to collapse
I've just unlocked mine by using the instructions in this thread: http://forum.xda-developers.com/showpost.php?p=12099386&postcount=6
I also just used the method posted above http://forum.xda-developers.com/showpost.php?p=12099386&postcount=6 and it worked.
100% safe? I'm not sure if it is.. I made sure I knew where my receipt was before trying just in case I screwed it up and had to take it back for warranty
EDIT:JUST TRIED TO DO IT ON MY BF'S PHONE
pretty sure I did the exact same instructions, but something must have went wrong, now his phone has no baseband no imei no service, sound doesn't work, won't factory reset or turn off. OOPS!
um I guess I'm screwed then -_-
fix for missing IMEI
I (stupidly) didn't make a backup of stl5 before attempting to get the unlock code from efs/mits/perso.txt and ended up with a phone that would boot correctly but had lost IMEI, wifi, BT, and kept rebooting every 5-10 minutes
How I managed to fix it:
Rooted the phone with Universal Androot
Battery pulled the phone and then booted
Connected with adb shell
-su
# dd if=/dev/block/stl5 of=/sdcard/stl5.rfs
# dd if=/sdcard/stl5.rfs of=/dev/block/stl5
# reboot
Waited a few minutes, then battery pulled again. When the phone booted, my IMEI, wifi and BT were all back again.
Massive thanks to posts by BlocK240 (http://forum.xda-developers.com/showpost.php?p=12187545&postcount=20) and FDAD (http://forum.xda-developers.com/showpost.php?p=12172648&postcount=1900) which I based this fix on
I hope this helps someone else whose i5500 got bricked in this way. Of course, I accept no responsibility if your phone gets even more fscked.
chancooluk said:
I've just unlocked mine by using the instructions in this thread: http://forum.xda-developers.com/showpost.php?p=12099386&postcount=6
Click to expand...
Click to collapse
hi there,
i'm just wondering how did you find the unlocking code? the link above just says that the guy finally done it. i'm new to all this, please if you can help me how to find the unlocking code on my galaxy europa. i have rooted phone and i have terminal installed. do i write word to word code on the terminal interface? how do we do it? please help me.
thanks.
Bricked my i5500
No it bricked mine
hello to all
well my problem is the same as many people...
I brick my i5500... its flash samsung on screen and turn off all time
when I put him in download mode and flash again whit Odin Downloader nothing hapens....only the same story...
please help...it must be some way to put it in work again but i cant find on forum
thanks in advance .....
Unfortunately this method too bricked my Europa and following slickandy's instructions I was still unable to fix the missing IMEI number. I had to return it to the original store and they luckily gave me a new one, I think I'll just purchase an unlock code from my service provider.
I, too, tried the "safe" method on a standard i5500. I'm somewhat familiar with Linux(everyday user for over a decade now), so figured no harm could come from just mounting and reading stl5.
How wrong I was. Lose IMEI, no phone connection, refused to shutdown(would restart after a few seconds with corrupt date and time).
This was a standard, unmolested phone, aside from the suggested method of root. No badly typed commands, just everything in the guide.
Don't do it. Codes are available for £9 on eBay. It's cheaper and safer to go down that route.
Dont use the stl5 method. Too risky.
Use the new bml5 method. That is 100% safe.
http://forum.xda-developers.com/showpost.php?p=17148825&postcount=334
Author of the OP should mention the bml5 method now to prevent unnecessary bricking.
Cheers
slickandy said:
I (stupidly) didn't make a backup of stl5 before attempting to get the unlock code from efs/mits/perso.txt and ended up with a phone that would boot correctly but had lost IMEI, wifi, BT, and kept rebooting every 5-10 minutes
How I managed to fix it:
Rooted the phone with Universal Androot
Battery pulled the phone and then booted
Connected with adb shell
-su
# dd if=/dev/block/stl5 of=/sdcard/stl5.rfs
# dd if=/sdcard/stl5.rfs of=/dev/block/stl5
# reboot
Waited a few minutes, then battery pulled again. When the phone booted, my IMEI, wifi and BT were all back again.
Massive thanks to posts by BlocK240 (http://forum.xda-developers.com/showpost.php?p=12187545&postcount=20) and FDAD (http://forum.xda-developers.com/showpost.php?p=12172648&postcount=1900) which I based this fix on
I hope this helps someone else whose i5500 got bricked in this way. Of course, I accept no responsibility if your phone gets even more fscked.
Click to expand...
Click to collapse
Hi, it happenned something similar to me. I got the unlock number, but when I rebooted the phone, it did not ask for it but the phone was actually unlockedl. However the IMEI was lost (all zeros). Fortunately I did not lose any connectivity, everything looks OK but IMEI is still zeros.
Now I doubt whether to test your method or not. Is it safe? I really would like to recover my IMEI to avoid future problems, but I would not like to brick a phone that actully works...
Thanks for sharing your results!
Hi guys I accidently wrote wrong NV items and now well it has been bootlooping for the last 1 year or maybe longer. I really do not want to give up on the phone but this is a hobby that I have and would to make one last attempt before I sell it in parts. I bought a data cable from the cellphoneshack.kom please stay away they sell items that do not work and it cost me $35.00 did will not give you a refund. The phone has the 1.490000 S-ON. I cannot get into recovery so that is gone. I sometimes get into the format all data but it does not change anything. ADB is not available since not rooted. When bootlooping it only gets to the 3 skate boarding droids and then the same cycle again. It will take the original roms but again it does not do anything. Fastboot will only take limited commands. Is there any way I can fix this phone. Thanks so much.
obonilla30,
Don't really understand what you said you've done to your phone to put it in its predicament. Can you elaborate on this, please?
The usage of adb is not really dependent on whether your phone is rooted or not, but rather on whether or not the adb service/daemon is running on your phone when you try to connect to it with your adb client on your PC.
The adb daemon on your phone gets started while in a custom recovery or when your phone boots normally (i.e., I usually see it after the SD card gets mounted), so you might not be getting far enough into the booting sequence to have it running (but it wouldn't hurt to keep trying to connect (i.e., do an "adb devices" to see if the adb daemon is running)).
Since you have the 1.49.0000 S-ON bootloader, you can't really do too much useful stuff (like flashing a custom recovery) with fastboot since you don't have the unsecured (S-OFF) bootloader.
I also don't really understand what you mean by "It will take the original ROMs..." -- can you elaborate on this?
Give us a little more detailed information about how your phone got into its current state and re. the questions above. This might help someone be able to help you out.
Cheers!
Hi,
"I sometimes get into the format all data but it does not change anything"
This mean you can go into recovery sometimes though?
can you mount your device from recovery?
which recovery you use?
If you can mount your sd, it mean you can use adb. just let us know this. Clarify more.
Have you tried to upload a good copy of the NV's, or can you not access through workshop, etc? If you cant do that you're going to have to use an RUU to repair. It needs to be a full flash as you dont know what is messed up in the NV's.
So I unsuccessfully attempted to root my HTC Amaze. I unlocked my bootloader successfully, and followed the directions from one of many online guides; specifically the "Zerg Rush Root" method (I hope you guys are familiar with the method, the guide on this forum seemed to be the manual way). The problem occurred towards the end of the process where the phone finally reboots itself into 'root' mode.
Let me describe the steps I took to get to that point. I apologize for the length, I wanted to be as in-depth as possible. Please bear with me.
After unlocking my bootloader, I would execute the "Zerg Rush" program; the command prompt would pop up, do its thing, and seem to finish with no errors. I press a key to finish and close the command prompt when it asks for it, and wait to see if my phone went through any changes. No change. So I reboot my phone. Again, no change. Thinking there might've been a hiccup somewhere, I repeat this whole process once more with the same result.
I then realize that I didn't extract the "Zerg Rush" program to the directory the online guide told me to extract it in. I didn't think the directory made a difference. So I moved the folder to the instructed directory and executed the program once more.
This time, in the command prompt, towards the end when it lists "xxx zerglings sent" and "finding a new path", there were extra commands that I haven't seen during the first two tries. The command prompt then gets to the point where it says "awaiting response from device" and my phone starts to reboot. This is when the problem occurred.
My phone got stuck in a boot-loop (the droid emblem rocketing upwards followed by the HTC logo) with no sound. This loop went on for about 15-20 min all the while with the command prompt continuing to display "awaiting response from device" until it finally booted and displayed the lock screen. I slide the unlocker and immediately notice the phone is sluggish, has no sound, doesn't vibrate on touch, and has no service. Apps and Widgets might've been missing from the homescreen too but I cannot confirm this with certainty.
After a few minutes of panicking, I decide to reboot the phone. Luckily, it booted like normal, in non-root mode. All the functions returned and is currently in its factory setting. Bootloader is still unlocked.
At this point, I'm scared to re-attempt the rooting. I fear the infamous "Bricking" of the phone which pretty much renders the it irreparable.
So my questions are:
What could've caused this? Could it be because of the first two unsuccessful attempts?
Are there any precautionary steps I should take to ensure my phone's safe operation?
Is it safe for me to attempt rooting again? And if so, which method should I use?
DougieJK said:
So I unsuccessfully attempted to root my HTC Amaze. I unlocked my bootloader successfully, and followed the directions from one of many online guides; specifically the "Zerg Rush Root" method (I hope you guys are familiar with the method, the guide on this forum seemed to be the manual way). The problem occurred towards the end of the process where the phone finally reboots itself into 'root' mode.
Let me describe the steps I took to get to that point. I apologize for the length, I wanted to be as in-depth as possible. Please bear with me.
After unlocking my bootloader, I would execute the "Zerg Rush" program; the command prompt would pop up, do its thing, and seem to finish with no errors. I press a key to finish and close the command prompt when it asks for it, and wait to see if my phone went through any changes. No change. So I reboot my phone. Again, no change. Thinking there might've been a hiccup somewhere, I repeat this whole process once more with the same result.
I then realize that I didn't extract the "Zerg Rush" program to the directory the online guide told me to extract it in. I didn't think the directory made a difference. So I moved the folder to the instructed directory and executed the program once more.
This time, in the command prompt, towards the end when it lists "xxx zerglings sent" and "finding a new path", there were extra commands that I haven't seen during the first two tries. The command prompt then gets to the point where it says "awaiting response from device" and my phone starts to reboot. This is when the problem occurred.
My phone got stuck in a boot-loop (the droid emblem rocketing upwards followed by the HTC logo) with no sound. This loop went on for about 15-20 min all the while with the command prompt continuing to display "awaiting response from device" until it finally booted and displayed the lock screen. I slide the unlocker and immediately notice the phone is sluggish, has no sound, doesn't vibrate on touch, and has no service. Apps and Widgets might've been missing from the homescreen too but I cannot confirm this with certainty.
After a few minutes of panicking, I decide to reboot the phone. Luckily, it booted like normal, in non-root mode. All the functions returned and is currently in its factory setting. Bootloader is still unlocked.
At this point, I'm scared to re-attempt the rooting. I fear the infamous "Bricking" of the phone which pretty much renders the it irreparable.
So my questions are:
What could've caused this? Could it be because of the first two unsuccessful attempts?
Are there any precautionary steps I should take to ensure my phone's safe operation?
Is it safe for me to attempt rooting again? And if so, which method should I use?
Click to expand...
Click to collapse
How long did it take for you to type this up?
Did you try this thread: [HOW TO] ROOT HTC RUBY / AMAZE 4G
In the x amount of time that you spent typing that up you could have already had it rooted.
Lol you just pulled a "too long, did not read" on me. I did spend a good minute trying to articulate my experience. My main concern was whether if it was safe to attempt rooting after what happened. I'll take your response as an All-Clear and get right to it. Thanks
DougieJK said:
Lol you just pulled a "too long, did not read" on me. I did spend a good minute trying to articulate my experience. My main concern was whether if it was safe to attempt rooting after what happened. I'll take your response as an All-Clear and get right to it. Thanks
Click to expand...
Click to collapse
Yeah pretty much.
DougieJK said:
At this point, I'm scared to re-attempt the rooting. I fear the infamous "Bricking" of the phone which pretty much renders the it irreparable.
Click to expand...
Click to collapse
It's pretty much impossible to brick your phone with S-ON right now
DougieJK said:
So my questions are:
What could've caused this? Could it be because of the first two unsuccessful attempts?
Are there any precautionary steps I should take to ensure my phone's safe operation?
Is it safe for me to attempt rooting again? And if so, which method should I use?
Click to expand...
Click to collapse
You should read the HOW TO Root guide, FAQ, and READ THIS FIRST,
Hi XDA,
I think I might need your help. Just got a new Kindle HDX 7. For once I decided to not root a device - sideload seemed sufficient for me. So I let it update from 13.3.0.5 up to 13.4.5.1, everything worked fine and I started to install apps. Following the new description here even managed to install GApps. Device worked for some time until recently. After a reboot the device was softbricked - colored kindle fire logo flashing. Luckily I have ADB access, hope that's worth something
Situation: Unrooted stock 4.5.1, GApps installed, soft brick, ADB access //solved http://forum.xda-developers.com/showpost.php?p=57084104&postcount=4
Last actions before softbrick: Add my google mail account to the built in mail function, GMail was also installed and configured. Switched on ADB over TCIP, just to check if it works. After a restart: Congratulations, device won't boot. Of course I wonder how my device could get bricked, since I never rooted...
Before digging into that further, would a factory reset be possible? Usuallly this would be the first thing to do, but for the Kindle this just seems to make the problem even worse. Or should I just do it anyway, see what happens, and if it fails send it back to Amazon? As mentioned: never rooted, so warranty shouldn't be voided.
Access via ADB: I'm not that familiar with Linux/Android, but it tried to look into it. (So far I haven't tampered with anything)
top shows com.androi.systemui woking at 50% cpu.
logcat: here comes the interesting part, apparantly com.google.android.gms crashes all the time and is restarted, on and on and on, causing the bootloop.. (Logcat attached for the curious ones) Nope, not the cause, tried to boot with the wifi router of (still bricked), different logcat. Attached it. Apparently google crashing is "normal". Any special tool to look at the logcat? Some IDE to search for/analyse critical errors? // Found a guide -> http://forum.xda-developers.com/showthread.php?t=2274119
Now I can only tell what the tablet is doing during the bootloop, but not what the main cause is, or even how to fix it. At first I tried to uninstall com.google.android.gms. Resulting in: failure, nothing changed.. Maybe the solution lies somewhere withing the capacities of the package manager?
In the logcat, at the end you can see that com.google.android.gms gets startet over and over again. yeah, for the first one, still trying to figure out the second one.
So, that's it, another guy whining about his broken tablet I hope that "new kind" of bootloop is a bit of a motivating challenge for all the experts here. Thank you very much!
Best regards, Grtschnk
You can do hard reset, no problem with this in your case.
And you can try something like this while bootlop:
Code:
adb uninstall com.google.android.gms
or maybe
Code:
adb shell
pm disable com.google.android.gms
need to try
Thank you very much for your answer! As mentioned hard reset would have been my first option, but was afraid to break it even more.
I already tried the commands you mentioned, no success, but things have changed anyway... edited my first post.
Is hard reset still possible? I'm studying the logcat to localize the error (ugh, feeling like 13 again when I tried to delete system32.exe on windows ME because it was causing errors xD ).
If hard reset, how to do on Kindle?
Code:
//Press Power + Volume Down
//Recovery Mode
//Reset
or
Code:
adb shell
recovery --wipe_data
or maybe give a first try by
Code:
adb shell
recovery --wipe_cache
Thank you very much again for your time! I really appreciate it. As someone who grew up with Windows 3.11, it's hard for me to get warm with the linux file system
//Press Power + Volume UP
//Recovery Mode
//Reset
about other commands, you can try, but I guess you cannot do any recovery commands without root.
ONYXis said:
//Press Power + Volume UP
//Recovery Mode
//Reset
about other commands, you can try, but I guess you cannot do any recovery commands without root.
Click to expand...
Click to collapse
Yay, worked! Dzięki! Up, down - always get them confused..