Related
So my nexus one froze today, and now whenever I pull the battery and put it back in, it will vibrate 7 times and wont boot. Is it bricked, or what can I do to fix this?
Thanks
What were u doin when this happened and what does the boot animation come up
Sent from my Nexus One using XDA App
I opened up the navigation app and it froze. Puller the battery and had that problem. I then decided to pull the battery, press the power button a few times to discharge the phone and it booted back up. So hopefully it wont happen again
Same thing happened to me. I was experimenting with an undervolted kernel which up until then had been behaving well. Received a bunch of texts and notifications simultaneously. By the time I got to my phone, it had gone to sleep. I was able to power on, but the screen was completely unresponsive. The powering on was also very delayed. I couldn't shutdown with the power button so I pulled the battery.
It could only do a 7-vibrate boot/freeze every single time I pulled the battery and replaced it. Finally, with the above advice, I left it out for several minutes, hit the power button a few times, then replaced the battery and got it to finally boot.
This happened to me today too, I took out my SD and it booted up just fine after that..not sure what happened. I checked my SD for errors but it didn't have any and had no problems after I put it back in.
hmm havent faced these errors yet, have u modded the rom at all?
mine just did it now when i changed the sd card.
taking the card out doesn't help.
i'm guessing it thinks the battery is flat or something similar, will try charging.
edit: just kept trying and it eventually worked.
I have the same problem, hitting the power button does nothing, I leave the battery out for ~ 5 minutes and eventually get a fastboot screen and 7 times vibrate, but no control, power button, volume and trackball not working. I have to pull the battery out, wait another 5 minutes or so and try again.
Does anyone have a clue about what that 7 times vibrate means? sounds like an error code.
If after have pulled out the battery for 5 minutes I keep pressed the volume down and the power, I eventually have a fastboot working screen, but choosing recovery from the menu takes me back to the fastboot screen with 7 times vibrate. Taking the card out or the sim does not make a difference.
How did I get here: Was using Cyanogen 2.2, rooted, screen froze one day, pulled the battery out and here I am.
Tried to do a reset with volume down and power, it freezed during the procedure and now it won't boot at all.
I'm still able just to start in fastboot. Recovery and clear storage do nothing useful. Booting normally gives me the nexus logo for a while and then the screen blanks after a few seconds.
I can do fastboot flash boot, but I can't do fastboot flash system, it just says sending and that's it:
Code:
[[email protected] apps]# ./fastboot erase userdata
erasing 'userdata'... FAILED (remote: not allowed)
[[email protected] apps]# ./fastboot erase cache
erasing 'cache'... OKAY
[[email protected] apps]# ./fastboot flash boot Passion\ Google\ WWE\ 1.01.1700.1_ERD79/boot.img
sending 'boot' (2044 KB)... OKAY
writing 'boot'... OKAY
[[email protected] apps]# ./fastboot flash system Passion\ Google\ WWE\ 1.01.1700.1_ERD79/system.img
sending 'system' (116663 KB)...
Any ideas anyone ?
alexxed said:
I'm still able just to start in fastboot. Recovery and clear storage do nothing useful. Booting normally gives me the nexus logo for a while and then the screen blanks after a few seconds.
I can do fastboot flash boot, but I can't do fastboot flash system, it just says sending and that's it:
Code:
[[email protected] apps]# ./fastboot erase userdata
erasing 'userdata'... FAILED (remote: not allowed)
[[email protected] apps]# ./fastboot erase cache
erasing 'cache'... OKAY
[[email protected] apps]# ./fastboot flash boot Passion\ Google\ WWE\ 1.01.1700.1_ERD79/boot.img
sending 'boot' (2044 KB)... OKAY
writing 'boot'... OKAY
[[email protected] apps]# ./fastboot flash system Passion\ Google\ WWE\ 1.01.1700.1_ERD79/system.img
sending 'system' (116663 KB)...
Any ideas anyone ?
Click to expand...
Click to collapse
Since you said you were using CyanogenMod, I will assume you are using CM6 RC2 not that it matters now. So you are running a custom recovery right? Try to wipe everything, data, cache, and the dalvik cache. Then flash a different ROM, either stock or any other really to see if that helps.
edited.
sent back to HTC
There are a batch of n1 that has this problem. I had bought a new att 3g version in june and returned it for a new. I also had the booting problem. It would constantly reboot or be stuck at the nexus boot logo. Its a hardware issue. Call google and they will transfer you to htc and work out a exchange or repair for you.
Sent from my GT-I9000 using XDA App
Vakman said:
Since you said you were using CyanogenMod, I will assume you are using CM6 RC2 not that it matters now. So you are running a custom recovery right? Try to wipe everything, data, cache, and the dalvik cache. Then flash a different ROM, either stock or any other really to see if that helps.
Click to expand...
Click to collapse
I'm trying to flash the stock image following the instructions here: #614850
Flashing hangs in various steps of flashing system.img, so I tried repeatedly until I succeeded, but still no success in booting afterwards, so I suspect I need to match the radio with the system as I've read that the radio boots before system. Right now I have FRF50 (4.06.00.12_7).
The problem is that once I leave the phone off for a while with battery in, the phone does not start in any mode (power, power + volume down, power + trackball) until I leave it with battery out for 2-3 days after which I can boot in any of the three modes above, the power button shows the nexus logo for a few seconds than the image scrambles and the phone goes off. If I choose to go in recovery I see the nexus logo forever.
Fastboot works, but as said, it hangs when flashing about 90% of the time.
I'll keep trying as sending off the phone for repair is a tricky option considering that I'm not in US, I haven't bought the phone from US, and so on.
Ive had this problem for awhile. It first started when i updated to froyo. I called htc Tech support an they told me it was probably caused by an app but i dont know if thats true or not. Iam curious to know what the 7 vibrations mean
In case you can't/don't want to send it back for warranty repair, it seems that leaving the phone charging for 12-24 fixes the issue (though it might look dead during those hours).
maxdadev said:
In case you can't/don't want to send it back for warranty repair, it seems that leaving the phone charging for 12-24 fixes the issue (though it might look dead during those hours).
Click to expand...
Click to collapse
Tried that and almost anything I could have imagine. Finally I sent the phone to HTC and they were kind enough to repair it free of charge, I only paid for the shipping to them, they paid the shipping back.
The interesting part is that I got the same phone (it has the same IMEI), but locked again, so I guess that means there is a way to lock the phone back.
I hate to revive an old thread, but it's probably better than making a new one about the same issue.
A friend of mine said this happened on his Nexus and now it won't boot past the "X" splash screen, and it vibrates 7 times. He gave it to me to try to fix, and I've done everything I can think of. When I try to use a PASSIMG.zip through Hboot the progress bar on the side fills, then it says "Checking PASSIMG.zip," but then it just returns to the Hboot screen.
I've tried using Fastboot to install Amon_Ra's recovery and Clockworkmod recovery, even a radio update, but any .img file I try tells me "FAILED (remote: signature verify fail)"
Has anyone found a fix for this, or have any suggestions?
If I have to call Google/htc can I still have it replaced, even if the bootloader has been unlocked, voiding the warranty?
Thanks.
You have to unlock the bootloader to use fastboot.
I have unlocked the bootloader. It says ***Unlocked*** at the top, it's still S-ON though.
I can't access recovery or ADB to tell if it's rooted or not, either.
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.33.0012
MICROP-0b15
RADIO-4.06.00.12_7
OK, that's weird then. I've never heard of fastboot failing before.
Nexus One running 2.2 on T-Mobile.
I rooted yesterday using one of the one click root apps. This went fine.
I installed several apps from the marketplace for rooted phones.
These include: Titanium Backup, ROM Manager, Quick Reboot, Eris Market Fix and a boot animation replacer
I did a backup using the ROM Manager first. Named it 'Original'
I ran the Eris Market Fix which said it was successful but needed a reboot. I figured since I was rebooting I might as well mess w/ the animation. I opened the app but it was not immediately apparent how it works so I left it alone for the time being. I used the quick reboot app to reboot.
The phone rebooted, I saw the initial X but it won't go further. At the point where the animation should start it just goes blank. About a minute after that the screen lights up very faintly and the buttons at the bottom (home, etc) light up and it just sits there.
If I reboot it (holding power, volume down and the trackball) then hold the volume down button I can get to the bootloader screen. Options are: fastboot, recovery, clear storage, simlock.
If I select recovery I get the exclamation point w/ the little android guy and it just sits there. From there if I push the volume up and power buttons I get the android system recovery. Options are: reboot system now, apply sdcard:update.zip, wipe data/factory, wipe cache partition.
I tried most of the options in both of those screens to no avail.
I just now figured out how to connect to it using fastboot so I guess I need to do something there just not super sure how to proceed.
I'm thinking that if I can get it back to stock, root and install the ROM Manager then i should be able to restore the backup I made earlier, is this correct?
Thanks in advance for the help.
crickets_chirping.mp3
...
It looks as though I should be able to load a recovery image and restore the backup I made before the incident according to what I've read since the original post.
Question: Since the ROM Manager used Clockwork to make the backup do I need to use it as well? Does it matter?
I have half a mind to just throw CM on there but there is some data in the backup that I'd like to have backed up by Titanium rather than a ROM image.
OK, trying to get clockwork to flash.
I get this:
fastboot flash recovery recovery-clockwork-2.5.0.7-passion.img
sending 'recovery' (2906 KB)... OKAY [ 0.478s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.978s
Had to fastboot oem unlock first
Then tried to flash clockworkmod, said it was successful, rebooted and got the '!'
Flashed Superboot
Rebooted
Flashed clockworkmod again
rebooted
started recovery (finally!)
It is now restoring my earlier made backup. Hopefully it will work.
Thanks for all the help guyz!
Five days before my note home button suddenly stop working.
so i decided to do Factory reset
by pressing Vol. up+Home+Power button as mentioned in Picture 1
Factory Reset goes smooth up to picture 11 i.e. finising point
after that screen goes black/blank after some time its rebooted itself and
Stuck at Samsung Logo.(as picture 14)
i have tried several time but no success
My phone Model No. written over Box_GT-N7000ZBAINU
My device is rooted with the help of Philz signed zip file
any more information required kindly let me Know
Thank YOU
mahesh_bharti said:
Five days before my note home button suddenly stop working.
so i decided to do Factory reset
by pressing Vol. up+Home+Power button as mentioned in Picture 1
Factory Reset goes smooth up to picture 11 i.e. finising point
after that screen goes black/blank after some time its rebooted itself and
Stuck at Samsung Logo.(as picture 14)
i have tried several time but no success
My phone Model No. written over Box_GT-N7000ZBAINU
My device is rooted with the help of Philz signed zip file
any more information required kindly let me Know
Thank YOU
Click to expand...
Click to collapse
My first guess is a bad battery.
If that is not the problem, you could probably fix it by flashing a rom, either a stock one using odin(Not ICS), or a custom one from recovery(Aryamod maybe)
If its a bad battery then, performing the setup while charger is connected should keep the phone ON.
Before this problem battery back up was almost 1 day with moderate use
can i try factory reset with charger plug in as @nokiamodeln91 said
Tried setup with charger connected but this time also at at the end of the setup phone hang rebooted itself after reboot stuck at Samsung logo
kindly help
Again,
Azeazezar said:
You could probably fix it by flashing a rom, either a stock one using odin(Not ICS), or a custom one from recovery(Aryamod maybe)
Click to expand...
Click to collapse
mahesh_bharti said:
Tried setup with charger connected but this time also at at the end of the setup phone hang rebooted itself after reboot stuck at Samsung logo
kindly help
Click to expand...
Click to collapse
Also before flash using Odin, boot into recovery, fomat system, data, cache and preload.. then go to advanced... reboot download and flash the rom with odin .. or use recovery to flash a custom rom.
i am newbie so kindly advice me which custom rom i should use with download link
i have to simply copy it to sd card and flsh it with Philz signed
or i have to do some more
kindly help
mahesh_bharti said:
i am newbie so kindly advice me which custom rom i should use with download link
i have to simply copy it to sd card and flsh it with Philz signed
or i have to do some more
kindly help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2575767
And yes, you just flash that rom from recovery, from your sd card.. After that you will want to do another factory reset, and clean cache.
Flashed with custom rom as you suggested @Azeazezar
but in this rom smoothness gone sluggish & poor touch sensitivity
what is the reason behind it
My stock JB was sooth enough
Use it for a day.
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
jggrnaut said:
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
Click to expand...
Click to collapse
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
berndblb said:
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
Click to expand...
Click to collapse
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
jggrnaut said:
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
Click to expand...
Click to collapse
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
berndblb said:
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
Click to expand...
Click to collapse
Well it has gotten worse and I think I have lost fastboot now. I downloaded the CWM from part 1 above and flashed it in fastboot. I typed fastboot reboot and now I am stuck in a bootloop still. It says "The device is unlocked" at top of Asus splash screen for about 15 seconds, screen turns black and the goes back to Asus splash screen.
I tried holding power and volume key to get back to fastboot but no luck. Any ideas?
Wow! You are really having some bad luck there!!
First the failed firmware update and now this.... Please post the commands you used to flash CWM.
I have no explanantion for this since you did not even boot into CWM.......
Unless..... the bad firmware flash left a command behind calling the stock recovery to do something (which in your case did not work anyway since it just looped) and now the bootloader tries to execute the command which is not "understood" by CWM. But that still does not explain why you cannot boot into the BL anymore......
Can you turn it off by long pressing power? Try every which way to get into fastboot. Without it there is not much you can do I'm afraid.
Try the restart pin hole (I believe it's on the left side of the tablet near the top) in conjunction with Volume Down, try leaving it alone for a while, try timing the button press somewhat differently - anything to get you into the BL again...
I feel very sorry for you, mate!!
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
jggrnaut said:
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
Click to expand...
Click to collapse
I don't know what happened before - maybe you were doomed since the bad firmware flash - but that last step sealed the coffin.
Using Wipe Data from the bootloader with a custom recovery installed is asking for trouble. Never ever do that.... Sorry, it's a brick. [emoji24]
Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance
Try to check your USB cable, most of the time charging issue is due to cable
shubham1358 said:
Try to check your USB cable, most of the time charging issue is due to cable
Click to expand...
Click to collapse
Cable is ok. I have another Le2 and it is charging with that cable very well
I am facing same problem. How you solve this issue? Blue led blinks after flashing any rom and bootloop.
xerol said:
Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance
Click to expand...
Click to collapse
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.
Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Forthe55 said:
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.
Click to expand...
Click to collapse
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view
Brother same thing happened to me, a week ago. I cant say about your problem but my problem was due to faulty power button. Actually due to that reason my phone actually kept restarting itself. It showed red light blinking while charging and wasn't able to bypass the optimizing app screen. I also thought it was a software issue but actually it wasn't. I spent about 2 hours figuring out what the actual problem was. The problem was: As we know when power button is hard pressed for about 10-15 seconds it reboots itself.
Although the repair shop guy didn't put new power button but he added a tiny piece of paper in between the power button and body housing to prevent the issue and voila the problem was solved.
delltech1 said:
Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view
Click to expand...
Click to collapse
Hi, Thanks. I actually did that first, flashing through qfil the same rom. it helped me to go to settings after umpteen attempts to go past language selection screen, and i was just able to oem unlock and enable usb debugging (actually after a 2nd partial failed flashing). the phone kept freezing within seconds of booting up. Now After i unlocked the bootloader and installing twrp and flashing many roms thru twrp, i am still having the same problem of booting up and freezing at start-up. cant flash again through qfil, as i will again loose the unlocked bootloader and twrp.
At least , now i can try different roms to see which can unbrick it. last one used was the twrp flashable rom based on eui (small eui by aurel) but it also freezes on language selection screen or beyond.
I am running out of ideas, lets see.
2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
If nothing helps it can be only a HW failure, maybe the power button, try usb 2.0 port during the flash process, i had issues with 3.0 on my pc, if that doesnt help.try a different cable, no more suggestions, sorry.
delltech1 said:
2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
Click to expand...
Click to collapse
My phone has been flashed multiple times by qfil method. And always it hangs at initial setup (so it boots up, but hangs at language selection or further up screens, before setup can complete and launcher could be loaded).
While trying to flash again with qfil once it stopped at 25 percent (because the battery went dead). Charged the battery and booted up the phone, and i was surprised it booted up. After 2-3 attempts i was able to reach the launcher screen and immediately enabled developer options and oem unlock / usb debugging. Only had few split seconds to do this and the phone froze again. After that i installed twrp and hence treying different roms. Most fail at setup.
Just tried MIUI 9PRO ROM. It also froze at setup multiple times, but once i was able to complete the setup and miui launcher is up , but it reboots or turn off the phone just after that. So cant do anything with the phone. Unsure of whether a newer bootloader will help in these freezing issues as i have been able to boot up at least in some roms only if for few seconds. Will try to tinker the settings of miui rom (if the phone let me do it before freezing/hanging). Lets see. Thanks for suggestions. More suggestions welcome, because i am still unsure weather this is a software or hardware related problem. I am guessing that it may have something to do with Google security as earlier i was getting msg that phone has been wrongly resetted and needs to verify with Google (but i couldn't get a chance to use the same account, as phone kept freezing at setup).
Did you fully charge the battery, if not let it fully charge in twrp. Flashing the roms in twrp works everytime or do you see any errors? Before you flash anything disconnect the usb cable.
---------- Post added at 09:54 PM ---------- Previous post was at 09:47 PM ----------
Try to flash the 21s bootloarder with modem, one zip using twrp. Go to fastboot mode and wipe modems. fastboot erase modem1st fastboot erase modem2st. Put the phone to flash mode and reimage with qfil. Before you do it write down both imeis, you can find them also on the original package on the backside. Also try to remove all sim cards from the phone and try a different cable. If nothing helps, hw issue, maybe the power button mention earlier in this thread.
After reflash skip everything at setup and reset phone to factory defaults. OEM is already unlocked, you dont have to do it again.
I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.
Forthe55 said:
I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.
Click to expand...
Click to collapse
Yeah sorry i screwed the command its fastboot erase modest1 modemst2, my bad.
Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)
Forthe55 said:
Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)
Click to expand...
Click to collapse
So you erased modems and reflashed with qfil right? If so i assume its a HW problem. Try the fix with the power button, i ran out of ideas
Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.
delltech1 said:
Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.
Click to expand...
Click to collapse
Did that also, the same problem. The phone freezes after the os is booted. I was wondering what is that isnt touched by flashing ( in download mode or fastboot mode or through twrp). I may need to tinker that. The roms are all fine in the sense they all stop at the same points. Something in the phones partition, which isnt touched by flashing? (There must be, as i flashed with qfil, the oem unlock remains, the bootloader didn't lock, and it remains unaffected by re-imaging)
Try this, maybe it helps:
https://forum.xda-developers.com/le-2/help/issues-installing-twrp-rom-le-s3-x522-t3618662/page2