Hi, guys.
I picked this xt1033 and it had the microusb input damaged, so i replaced it, but since then, it got stucked on motorola logo.
I guessed that the system got corrupted and then i uploaded some new system. It went through nicely, but when it rebooted got stucked again. So, i'ved unlocked it bootloader (to start from zero) and re-locked it, putting a new system from the ground and apparently it ended well, but it got stucked again on logo (and later i've founded that it didn't lock). I've begin to put TWRP to install a custom rom on it (to see if i've could pass throgh that) and founded that my files was still there (EVEN AFTER I'VE UNLOCKED THE BOOTLOADER, who would've erased everything from inside), system, images and even whatsapp files. MTP Service give-me a taste of what was inside and everything was there, nothing corrupt.
So i'ved erased it and put a new rom, TWRP said it did it and was asking for reboot, so i did.
And it got stucked again and nothing was erased.
So the thing is, it's internal storage is freezed and i can't do anything with it.
Could you guys help me? Thanks in advance.
i may be wrong here... but i dont remember unlocking bootloader erased my data.... but it was long time ago...
coming back to your problem.. have you tried using repair option in twrp?
also try wiping all partitions and do a recovery reboot to see if it works
access_unlimited said:
i may be wrong here... but i dont remember unlocking bootloader erased my data.... but it was long time ago...
coming back to your problem.. have you tried using repair option in twrp?
also try wiping all partitions and do a recovery reboot to see if it works
Click to expand...
Click to collapse
Already done.
I could only enter TWRP by boot it on bootloader, not flashing ('cuz was impossible to write on memory and was saying that the flash was successful).
TWRP said it wipe it completely without any error, but it's was there.
And by ordering to reboot on Recovery Mode, it went back to original recovery and trying to erase from there do the same thing (said that was complete, but everything is still there).
Same problem here, this is a problem with emmc bricked
Related
hello, I have a problem with a desire s phone which keeps booting into recovery mode when i turn it on. here's my step by step of what I did that got me into this predicament.
the phone had a stock 1.48 asia rom 0.98.0002 bootloader locked, and unrooted. so first I ran revolutionary had no problems there, had a revolutionary logo on my bootloader afterwards and the bootloader version was now 6.98.0002 or something I forget. anyway the next thing i did was I downloaded the stock euro rom 2.10.401.9 and extracted the rom.zip then renamed it to PG88img.zip copied it to the memcard ran fastboot, then fastboot automatically installed the zip after installation restarted the phone, now the phone was stuck on the white htc screen, so I ran recovery press the power and vol up and did a factory reset, had no luck with it still stuck on htc screen, now after reading a lot of threads, downloaded the ENGpg88img bootloader flashed it using fastboot and it was successful, the revolutionary logo was gone and the bootloader was now 6.98.0000 ( PG880000) but now when I rebooted the phone it would go directly back to recovery!! So the next thing i did was ran the euro rom again from the memcard thru fastboot and it updated the bootloader to the newest version and had a "locked"on top of the screen, so i did a boot unlock using htcdev and now its unlocked, then downloaded the clockwork recovery for saga then flashed it using fastboot with no problems. so now when I turn on the phone it goes straight to clockwork recovery! So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
long story short, I can only use fastboot, and if I use clockwork mod recovery to mount system i can do some adb commands. i also tried putting it in fastboot and ran an official RUu but I always get error 150. any help would be greatly appreciated.
It seems that your chip is gone. I have the same problem (boot looping) and had to try reclamation by phone provider. Find thread with "boot looping", or "white screen". You will find some software for a searching of your chip. Finaly all depends on your mobile vendor
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Could you tell us how you solved it?
batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Hi, I have the same problem with HTC Desire.
Could you tell how you solved this please?
I don't know if he did what he wrote, but a big mistake was the last step.
batmite said:
So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
Click to expand...
Click to collapse
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Sent by my fingers to your head.
eyahl said:
I don't know if he did what he wrote, but a big mistake was the last step.
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Click to expand...
Click to collapse
Have to disagree with you there, what he said was
installed ROM
wiped DATA
wiped CACHE
rebooted
The ROM ZIP would have been flashed into SYSTEM not DATA, so wipe shouldn't have caused a problem
question is did BOOT flash ok?
so i have been using multirom and reflashed a rom to my internal rom. then i rebooted it and it is stick with a blank screen after the "google" logo and stuck there. when i go to twrp, it prompts me for a password that i have not set. I have read that this happens if you dont reboot after unlocking but i did that when i first unlocked the bootloader and have never ran into any problems flashing many roms till now. any ideas???
onecrzyasian said:
so i have been using multirom and reflashed a rom to my internal rom. then i rebooted it and it is stick with a blank screen after the "google" logo and stuck there. when i go to twrp, it prompts me for a password that i have not set. I have read that this happens if you dont reboot after unlocking but i did that when i first unlocked the bootloader and have never ran into any problems flashing many roms till now. any ideas???
Click to expand...
Click to collapse
Did u try to wipe "format data" as explained by Dess_Troy?
This happened to me too when I flashed a kernel without making sure it was correct for the rom I was running. I just forced it to reboot into recovery and it turned out fine. Have you tried that?
Sent from my Nexus 5 using Tapatalk
If you have just used fastboot oem unlock, you should let the device boot up normally first before trying to install TWRP. If you boot TWRP first before booting normally, you will be prompted for a password. Hit cancel and got to Wipe -> Format Data. Type yes at the prompt and hit the "enter" key. Hit the home button at the bottom and Reboot -> Recovery. Unlocking the device will cause you to lose all userdata, apps, pictures, downloads, etc.
Click to expand...
Click to collapse
Source: http://www.teamw.in/project/twrp2/205
It'll be ok
This has happened to me a couple times, all I had to do was hit cancel and it went into recovery, no password needed. Just needed to reflash Multirom.
hmm wonder if i could have reflashed the multirom. cuz when i tried to reflash roms or try to flash another roms or anything, it wouldn't work. said the files were all encrypted. under the file manager, there was no accessible or viewable files. completely locked out. I ended up doing a back up by going into bootloader and pulling files to my desktop then did a stock flash.
as for the reformatting, i've shouldn't/wouldn't want to do that because i have already unlocked the bootloader, did the fastboot reboot and flashed countless roms and kernels. I think there was some sort of corruption that screwed with something. And i really didn't want to lose all my data be reformatting it.
only booting into recovery and clicking cancel when prompted password made me completely locked out. said that everything was encrypted so i was out of luck.
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.
I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you
I have almost the same problem as if the fastboot not install anything despite not display errors
great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.
do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.
Hello guys,
I have a problem, I hope you can help me with.
I used to have an EOS ROM. I decided to do factory reset and thats when my problems started. It didn't boot up anymore. After entering recovery I noticed it couldn't mount System partition. I tried reinstalling the ROM, but no success. Everytime I entered recovery, the System checkbox wasnt marked. So I decided to go back to stock, using http://androidforums.com/threads/return-your-xoom-to-stock.653230/. Now it is stuck at Logo screen and can't enter Recovery. (Goes to Reading ODM fuse, but not any further). I can still enter Fastboot and my laptop detects the tablet, when hooked up to it.
Please help me push the Recovery, cuz I'm getting "device not found" from ADB. I'm kinda lost here... Any help would be appreciated!
Update
I managed to install TWRP, but still can't mount System Partition. On wipe I get "Failed"when trying to clean the system part. I have tried Clockwork, it didn't help either.
Cmon guys! I don't want to JTAG it yet.
HexBox said:
Cmon guys! I don't want to JTAG it yet.
Click to expand...
Click to collapse
I am not very knowledgable about flashing, but one suggestion has come to my mind: if you can now get into TWRP (it wasn't clear whether you could based on your last post), try flashing a ROM without trying to clean the system partition. Just make sure the ROM matches the TWRP (i.e., big part ROM with big part TWRP).
Oh - another thought - folks in a number of threads have stated you need to explicitly follow both the recovery and ROM instructions for the XOOM. If you miss a step, people have had issues.
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:
Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery
Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!
OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.
It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.