Related
Hi every body.I installed virtuous unity on my desire s.Yesterday I changed radio of my phone and it's os crashed.I think it's fastboot is enabled, because I can't access to bootloader by keeping volume down and press power button. Thus I can't restore my backup.Can anybody help me??Thanks alot.
ebishirani said:
Hi every body.I installed virtuous unity on my desire s.Yesterday I changed radio of my phone and it's os crashed.I think it's fastboot is enabled, because I can't access to bootloader by keeping volume down and press power button. Thus I can't restore my backup.Can anybody help me??Thanks alot.
Click to expand...
Click to collapse
Did it crash during the radio flash?
Have you tried removing the battery, putting it back in the trying to get into bootloader?
Sent from my HTC Desire S using Tapatalk
ebishirani said:
Hi every body.I installed virtuous unity on my desire s.Yesterday I changed radio of my phone and it's os crashed.I think it's fastboot is enabled, because I can't access to bootloader by keeping volume down and press power button. Thus I can't restore my backup.Can anybody help me??Thanks alot.
Click to expand...
Click to collapse
1) What message have you got after updating radio? success or not.
2) have you checked the md5 of radio file before update
->anyway connect ur phone to the computer
-> make sure u have installed all htc drivers and ADB components
-> type adb reboot recovery
if you can go into recovery, now you can flash any ROM
Thanks guys.After updating the radio I got "successful ..." massage.Then I reboot my phone.After rebooting, HTC logo appears and stayed in this page. I waited a few minutes but nothing happened. Then I tried to go to the bootloader to restore my backup,but I couldn't access to the bootloader.(
I removed the battery but it didn't work.
---------- Post added at 03:03 PM ---------- Previous post was at 03:03 PM ----------
Thanks guys.After updating the radio I got "successful ..." massage.Then I reboot my phone.After rebooting, HTC logo appears and stayed in this page. I waited a few minutes but nothing happened. Then I tried to go to the bootloader to restore my backup,but I couldn't access to the bootloader.(
I removed the battery but it didn't work.
ebishirani said:
Thanks guys.After updating the radio I got "successful ..." massage.Then I reboot my phone.After rebooting, HTC logo appears and stayed in this page. I waited a few minutes but nothing happened. Then I tried to go to the bootloader to restore my backup,but I couldn't access to the bootloader.(
I removed the battery but it didn't work.
---------- Post added at 03:03 PM ---------- Previous post was at 03:03 PM ----------
Thanks guys.After updating the radio I got "successful ..." massage.Then I reboot my phone.After rebooting, HTC logo appears and stayed in this page. I waited a few minutes but nothing happened. Then I tried to go to the bootloader to restore my backup,but I couldn't access to the bootloader.(
I removed the battery but it didn't work.
Click to expand...
Click to collapse
Can you turn the phone at all, even if it gets stuck at the splash screen?
Do you have adb setup?
If you do turn the phone on and type "adb reboot recovery" you may have to type it a few times before it will reboot.
Sent from my HTC Desire S using Tapatalk
sagarda7 said:
1) What message have you got after updating radio? success or not.
2) have you checked the md5 of radio file before update
->anyway connect ur phone to the computer
-> make sure u have installed all htc drivers and ADB components
-> type adb reboot recovery
if you can go into recovery, now you can flash any ROM[/QUOT
Unfortunately I haven't checked the md5 of radio file
I installed HTC drivers and connected my phone to PC but computer couldn't detect my phone.(
Click to expand...
Click to collapse
Did you try adb?
Sent from my HTC Desire S using Tapatalk
cjward23 said:
Can you turn the phone at all, even if it gets stuck at the splash screen?
Do you have adb setup?
If you do turn the phone on and type "adb reboot recovery" you may have to type it a few times before it will reboot.
When I turn on my phone, the splash screen appears and the phone stick in this state and no button dose work.I can't do any thing.
Click to expand...
Click to collapse
ebishirani said:
cjward23 said:
Can you turn the phone at all, even if it gets stuck at the splash screen?
Do you have adb setup?
If you do turn the phone on and type "adb reboot recovery" you may have to type it a few times before it will reboot.
When I turn on my phone, the splash screen appears and the phone stick in this state and no button dose work.I can't do any thing.
Click to expand...
Click to collapse
ADB?
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
Look in my signature for various links...
Download and extract the adb & fastboot into a directory on your PC. Ensure that you have HTC drivers installed on you PC if not also download and install the link in my signature.
Then fire up a CMD on your PC, go to directory where adb is and issue the command
Code:
[B][COLOR="Blue"]adb reboot recovery[/COLOR][/B]
which should take you into recovery, where you'll be able to reflash or restore a nandroid backup from.
ben_pyett said:
Look in my signature for various links...
Download and extract the adb & fastboot into a directory on your PC. Ensure that you have HTC drivers installed on you PC if not also download and install the link in my signature.
Then fire up a CMD on your PC, go to directory where adb is and issue the command
Code:
[B][COLOR="Blue"]adb reboot recovery[/COLOR][/B]
which should take you into recovery, where you'll be able to reflash or restore a nandroid backup from.
Click to expand...
Click to collapse
Wonder why he can't get in to the bootloader though?
Sent from my HTC Desire S using Tapatalk
cjward23 said:
Wonder why he can't get in to the bootloader though?
Click to expand...
Click to collapse
Odd, although he has yet to comment on the success or failure of ADB? I suspect that he may not fully understand or be following our suggestions?
Could be that volume buttons broken, this happened to someone the other day - although in that case they were stuck in!
He has other options open to him
Code:
adb reboot [COLOR="Green"] --- then hold down volume buttons[/COLOR]
adb reboot bootloader
ben_pyett said:
Look in my signature for various links...
Download and extract the adb & fastboot into a directory on your PC. Ensure that you have HTC drivers installed on you PC if not also download and install the link in my signature.
Then fire up a CMD on your PC, go to directory where adb is and issue the command
Code:
[B][COLOR="Blue"]adb reboot recovery[/COLOR][/B]
which should take you into recovery, where you'll be able to reflash or restore a nandroid backup from.
Click to expand...
Click to collapse
Thanks a lot Ben.The speed of my internet is so slow (.I will download mentioned files and do your instructions.If it don't work,I will come back and announce it.
best regards.
ben_pyett said:
Odd, although he has yet to comment on the success or failure of ADB? I suspect that he may not fully understand or be following our suggestions?
Could be that volume buttons broken, this happened to someone the other day - although in that case they were stuck in!
He has other options open to him
Code:
adb reboot [COLOR="Green"] --- then hold down volume buttons[/COLOR]
adb reboot bootloader
Click to expand...
Click to collapse
Hi guys.I installed htc drivers(by this package: HTCDriver3.0.0.007) and adb folder which contains the files listed in the attached picture.When I typed "abd reboot recovery",in cmd I give this error massage: "device not found". please help me.(
ebishirani said:
Hi guys.I installed htc drivers(by this package: HTCDriver3.0.0.007) and adb folder which contains the files listed in the attached picture.When I typed "abd reboot recovery",in cmd I give this error massage: "device not found". please help me.(
Click to expand...
Click to collapse
And you tried this with the device turned on?
Sent from my HTC Desire S using Tapatalk
cjward23 said:
And you tried this with the device turned on?
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
Yes,When it was turn on even When it was turn off.But in both situation,There wasn't any successful.
ebishirani said:
Yes,When it was turn on even When it was turn off.But in both situation,There wasn't any successful.
Click to expand...
Click to collapse
And you tried the cmd a few times? Even though it looks like it is frozen on the splash screen there is stuff going on in the background. and adb will only start working after a certain point
Sent from my HTC Desire S using Tapatalk
cjward23 said:
And you tried the cmd a few times? Even though it looks like it is frozen on the splash screen there is stuff going on in the background. and adb will only start working after a certain point
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
I try it a few times,but there isn't any successful.The only message i give is:"device not found"
---------- Post added at 04:56 PM ---------- Previous post was at 04:26 PM ----------
The radio file that I flashed it to my phone is : Radio_12.59.60.26U_26.11.04.21_M.
The package of this file did not have "android-info.txt" file.To solve this problem I copied this file(android-info) from another radio file to the "Radio_12.59.60.26U_26.11.04.21_M" package.By did this I could install the radio on my phone.But after rebooting the device, it haven't worked.Can anybody help me to solve this problem?
thanks a lot.
---------- Post added at 05:44 PM ---------- Previous post was at 04:56 PM ----------
Nobody can help me??(
O!
ebishirani said:
I try it a few times,but there isn't any successful.The only message i give is:"device not found"
---------- Post added at 04:56 PM ---------- Previous post was at 04:26 PM ----------
The radio file that I flashed it to my phone is : Radio_12.59.60.26U_26.11.04.21_M.
The package of this file did not have "android-info.txt" file.To solve this problem I copied this file(android-info) from another radio file to the "Radio_12.59.60.26U_26.11.04.21_M" package.By did this I could install the radio on my phone.But after rebooting the device, it haven't worked.Can anybody help me to solve this problem?
thanks a lot.
---------- Post added at 05:44 PM ---------- Previous post was at 04:56 PM ----------
Nobody can help me??(
Click to expand...
Click to collapse
Where did you get this RADIO from? please provide a link to the source so that I can see.
Flashing a phones radio is one of the most potentially damaging things that you can do to your device and hacking a radio file prior to flashing is highly risky.
ben_pyett said:
Where did you get this RADIO from? please provide a link to the source so that I can see.
Flashing a phones radio is one of the most potentially damaging things that you can do to your device and hacking a radio file prior to flashing is highly risky.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=996630, This is a link to this radio file.
---------- Post added at 06:33 PM ---------- Previous post was at 06:27 PM ----------
ebishirani said:
http://forum.xda-developers.com/showthread.php?t=996630, This is a link to this radio file.
Click to expand...
Click to collapse
and it is another link : http://www.mediafire.com/?e5u78r5s3hk3kpy
---------- Post added at 06:37 PM ---------- Previous post was at 06:33 PM ----------
Oh my god!!!!!I didn't attention to the forum title,,,This radio file,is desire Hd's radio file.
---------- Post added at 06:55 PM ---------- Previous post was at 06:37 PM ----------
is it possible that the bootloader of the phone has damaged?If it is true,How can I modify the bootloader?Is it possible?
Hi
After trying to install crombi on tf700 using twrp 2.7 something went wrong and now tablette is bootlooping on twrp screen.
Cpnnected the tablette to laptop and nothing appears in the M'y Computer Windows.
Checked on device manager and found 'transformer' writen there with yellow exclamation Mark.
Tried to update driver with nô success.
Any help Will be greatly appreciated
Thanks
We need more information.
What did you come from?
What's your bootloader and rom versions?
Did you do a full wipe?
Describe in detail the procedure you followed.
berndblb said:
We need more information.
What did you come from?
What's your bootloader and rom versions?
Did you do a full wipe?
Describe in detail the procedure you followed.
Click to expand...
Click to collapse
Hi and thanks for the reply.
The tablet was on the latest Cromi-x and bootloader.
Did a full wipe and begun installing crombi
The tablet was stuck a long time on formatting so I had to regoot
After the reboot it was unable to moiunt E,
Tried to do another full wipe and now the tablet is just bootlooping on the TWRP splashscreen.
Any suggestion?
Formatting with TWRP 2.7 can take 90 minutes. You should not have interrupted it.
Can you get into fastboot?
Or alternatively you can try to get an adb connection when the tablet is looping.
berndblb said:
Formatting with TWRP 2.7 can take 90 minutes. You should not have interrupted it.
Can you get into fastboot?
Or alternatively you can try to get an adb connection when the tablet is looping.
Click to expand...
Click to collapse
Thanks for the answer so just connect the tablet, open cmd and do adb devices ?
Will try it in 30 min as I am not home
Tried the adb devices on a command windows in the platform-tools directory and nothing comes after hitting enter
Anything else to try?
What about fastboot? Boot with Volume Down and Power. Then try
'fastboot devices'
Sent from my DROID4 using Tapatalk
allotesting said:
Thanks for the answer so just connect the tablet, open cmd and do adb devices ?
Will try it in 30 min as I am not home
Tried the adb devices on a command windows in the platform-tools directory and nothing comes after hitting enter
Anything else to try?
Click to expand...
Click to collapse
Nothing? something must come up. What does it say? Command not found? No devices found?
sbdags said:
Nothing? something must come up. What does it say? Command not found? No devices found?
Click to expand...
Click to collapse
Hi
When I try the fastboot devices command it comes back to the invite with nothing written
When I try the adb devices nothing after list of devices attached
And the tablet keeps on bootlooping on the teamwin splash screen
And as already stated in device manager I find the mention transformer with yellow mark
Hi
Something new after I tried to update driver
Tried the fastboot command and it found something
It gives me s bunch of numbers and letters and recovery at the end
Is it good doctor?
Tried to install TWRP using fastboot -I 0x0B05 flsh recovery TWRP.blob and it sots there with the message <waiting for device> and tablet is still bootlooping:crying:
allotesting said:
Tried to install TWRP using fastboot -I 0x0B05 flsh recovery TWRP.blob and it sots there with the message <waiting for device> and tablet is still bootlooping:crying:
Click to expand...
Click to collapse
Are you in the boot loader when you issue that command?
By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks
allotesting said:
By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks
Click to expand...
Click to collapse
Yes that is normal. What happens when you flash twrp with fasboot. What does it report back?
allotesting said:
By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks
Click to expand...
Click to collapse
Ok, I think we need to clear up some things:
If the tablet is bootlooping it cannot be in the bootloader and fastboot mode (you are in the bootloader menu when you see the 3 icons: RCK, Android, Wipe Data). But if you see the adb interface in Device Manager while it is looping you should have an adb connection and
Code:
adb devices
should return a similar but different string of numbers and letters.
Code:
adb reboot-bootloader
should boot you into the bootloader which is also fastboot mode.
In fastboot you should be able to flash TWRP with the command you posted, minus the typos naturally.
It has to be
Code:
fastboot devices
and it has to return the string of letters and numbers, then:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Try that and report back
Hi there, I have the exact same problem. I tried searching all over about the time for a full wipe and couldn't find anything. So after about an hour I hard powered down. Of course, when I started researching the recovery look, I found the info (roughly 90-120 minutes). Here is what I have done to try to rectify, perhaps you can help. I booted into the bootloader and ran the following commands:
C:\>fastboot devices
015d2bbcc413ea10 fastboot
C:\>cd adb
C:\adb>dir
Volume in drive C has no label.
Volume Serial Number is 48F6-D102
Directory of C:\adb
04/29/2014 11:49 PM <DIR> .
04/29/2014 11:49 PM <DIR> ..
04/25/2014 06:59 AM 819,200 adb.exe
04/25/2014 06:59 AM 96,256 AdbWinApi.dll
04/25/2014 06:59 AM 60,928 AdbWinUsbApi.dll
04/25/2014 06:59 AM 160,256 fastboot.exe
04/29/2014 11:49 PM 6,443,112 openrecovery-twrp-2.7.0.0-tf700t.blob
5 File(s) 7,579,752 bytes
2 Dir(s) 672,096,153,600 bytes free
C:\adb>ren openrecovery-twrp-2.7.0.0-tf700t.blob twrp.blob
C:\adb>dir
Volume in drive C has no label.
Volume Serial Number is 48F6-D102
Directory of C:\adb
04/29/2014 11:50 PM <DIR> .
04/29/2014 11:50 PM <DIR> ..
04/25/2014 06:59 AM 819,200 adb.exe
04/25/2014 06:59 AM 96,256 AdbWinApi.dll
04/25/2014 06:59 AM 60,928 AdbWinUsbApi.dll
04/25/2014 06:59 AM 160,256 fastboot.exe
04/29/2014 11:49 PM 6,443,112 twrp.blob
5 File(s) 7,579,752 bytes
2 Dir(s) 672,096,088,064 bytes free
C:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6292 KB)...
OKAY [ 2.459s]
writing 'recovery'...
OKAY [ 7.564s]
finished. total time: 10.023s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.022s
Click to expand...
Click to collapse
When I reboot into the bootloader and click RCK I get the TEAMWIN logo (blue screen). About every 2-3 seconds the screen goes black and the TEAMWIN logo shows again.
Thoughts?
---------- Post added 30th April 2014 at 12:16 AM ---------- Previous post was 29th April 2014 at 11:56 PM ----------
I decided to play around a little more to see what I could do. I pushed TWRP v2.6.3.2 to the device replacing v2.7. Finally I was able to get into TWRP. However, now I am stuck. TWRP asks me for a password that was never set (I don't have one). I hit cancel and the main menu and I show as having -1mb of internal storage.
If I try any commands, I am told that there aren't permissions to access the partitions. I feel like I am getting closer.
If I tell TWRP to FORMAT DATA in the WIPE menu, recovery restarts and asks me for my password again.
Thoughts?
BigKenW said:
Hi there, I have the exact same problem. I tried searching all over about the time for a full wipe and couldn't find anything. So after about an hour I hard powered down. Of course, when I started researching the recovery look, I found the info (roughly 90-120 minutes). Here is what I have done to try to rectify, perhaps you can help. I booted into the bootloader and ran the following commands:
When I reboot into the bootloader and click RCK I get the TEAMWIN logo (blue screen). About every 2-3 seconds the screen goes black and the TEAMWIN logo shows again.
Thoughts?
---------- Post added 30th April 2014 at 12:16 AM ---------- Previous post was 29th April 2014 at 11:56 PM ----------
I decided to play around a little more to see what I could do. I pushed TWRP v2.6.3.2 to the device replacing v2.7. Finally I was able to get into TWRP. However, now I am stuck. TWRP asks me for a password that was never set (I don't have one). I hit cancel and the main menu and I show as having -1mb of internal storage.
If I try any commands, I am told that there aren't permissions to access the partitions. I feel like I am getting closer.
If I tell TWRP to FORMAT DATA in the WIPE menu, recovery restarts and asks me for my password again.
Thoughts?
Click to expand...
Click to collapse
It seems as if TWRP thinks your data partition is encrypted.
Boot into recovery, make sure you have an adb connection with
Code:
adb devices
if that returns a string of letters and numbers try
Code:
adb killall recovery
This should get you back to recovery and then try to format data again.
Good luck
berndblb said:
It seems as if TWRP thinks your data partition is encrypted.
Boot into recovery, make sure you have an adb connection with
Code:
adb devices
if that returns a string of letters and numbers try
Code:
adb killall recovery
This should get you back to recovery and then try to format data again.
Good luck
Click to expand...
Click to collapse
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
Click to expand...
Click to collapse
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
---------- Post added at 01:18 AM ---------- Previous post was at 12:55 AM ----------
BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
Click to expand...
Click to collapse
Alright, nothing I can do will fix this thing. The internal drive shows 0mb. I even tried installing CWM and I can't mount any partitions. I would like to return to full stock. I can't seem to find anything like an RUU or other tool to do this. Can someone please direct me to the best thread to do so?
After I am back stock I will unlock the bootloader again.
I will follow all the commands when I will be back from work. It's 3:30 here in Montreal thanks guys
BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
---------- Post added at 01:18 AM ---------- Previous post was at 12:55 AM ----------
Alright, nothing I can do will fix this thing. The internal drive shows 0mb. I even tried installing CWM and I can't mount any partitions. I would like to return to full stock. I can't seem to find anything like an RUU or other tool to do this. Can someone please direct me to the best thread to do so?
After I am back stock I will unlock the bootloader again.
Click to expand...
Click to collapse
To return to stock just download the Asus firmware, unzip it once and flash the resulting zip in recovery.
Your bootloader will stay unlocked. You just have to flash a custom recovery again, reboot and then flash the rom.
allotesting said:
I will follow all the commands when I will be back from work. It's 3:30 here in Montreal thanks guys
Click to expand...
Click to collapse
Hi all
Back from work but all the commands were uselee
In device manager I have ASUS android ADB interface after updating manually the 'transformer' that I had with the yellow matk
When trying adb devices it comes with 0123456789ABCDEF all the hexadecimal digits so seems to me that the machine does not recognize the tablet itself
When trying fastboot devices and hit enter it comes back to the >invite
When trying adb reboot-bootloader it just sits there with even no >invite
Forgot to mention that the word recovery comes after the 0123456789ABCDEF on the adb devices
Anything else to try? Thanks
For some reason my phone wouldn't accept the OTA update to 44S, but I was happy with 38R so stuck with that.
Now I see lollipop is coming, and (as I read it) some of the updates in 44S and the latest update contain updates which are required for lollipop, so I decided to upgrade by flashing it.
Stupid decision to do before my morning coffees, but there you go.
I downloaded the unofficial XNPH44S rom with a plan to install via TWRP.
Here is where I made rookie mistake number one; I wiped the phone before I adb pushed the rom zip across.
A little googling, and I discovered adb sideload so I think all is not lost.
Sideloading the rom seemed to work, so I rebooted back into TWRP (v2.8.1.0) to install the rom, and now my screen is unresponsive. I can't press any of the options, and pressing the volume or power buttons just brings up the swipe to unlock, which of course does nothing because the screen won't respond.
I can't go back to fastboot and install the rom that way (which, with hindsight, I realise was probably my best option in the first place) because I have no OS installed, and I can't do anything with TWRP because the buttons don't work.
Any suggestions, or am I screwed?
When it's connected via adb isn't there a command to reboot into boot loader? Adb reboot-bootloader or something? Google around.
Or turn it off and press vol up + power I think that takes you to bootloader mode. Check the noob guides for commands and steps I can't remember off hand what they are
---------- Post added at 08:04 PM ---------- Previous post was at 08:01 PM ----------
It's weird that twrp is unresponsive though...
ek69 said:
When it's connected via adb isn't there a command to reboot into boot loader? Adb reboot-bootloader or something? Google around.
Or turn it off and press vol up + power I think that takes you to bootloader mode. Check the noob guides for commands and steps I can't remember off hand what they are
---------- Post added at 08:04 PM ---------- Previous post was at 08:01 PM ----------
It's weird that twrp is unresponsive though...
Click to expand...
Click to collapse
I was being a noob and thinking that because 'adb devices' was showing none that fastboot wouldn't work.
Went back to 38R, installed 44S OTA (which made my phone bootloop as it has every other time I tried to install it) then did an adb sideload of the 44s to 05Q update.
Phone fixed, and up to date - now I just have to reinstall everything and remember passwords.
Q&A for **TWRP** custom recovery for IDOL3 6045
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for **TWRP** custom recovery for IDOL3 6045. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
stuck on twrp bootloop
stuck on twrp boot loop. any suggestions? i followed instructions as posted, but when rebooted into twrp and tried to reboot system, i keep going back to twrp. thanks
Heyy
I have the same problem,, although i did a backup and then a deleted everything cause it was looping,,, how do i fix everything to the original condition,, i won't be doing this again,, my model is an i version.. Although mine is not booting into twrp ,, just the original..
Restoring my backup does not work
I tryed everything,, i know not to do this anymore I think it's broke forever.
If you can get into twrp it can most likely be fixed.
Download the system image and try to install it. May need to put it on sdcard or USB otg.
This is all Alcatel's fault for not releasing anything when we kindly asked...
Where is the system image?
neilownz said:
If you can get into twrp it can most likely be fixed.
Download the system image and try to install it. May need to put it on sdcard or USB otg.
This is all Alcatel's fault for not releasing anything when we kindly asked...
Click to expand...
Click to collapse
---------- Post added at 12:30 AM ---------- Previous post was at 12:20 AM ----------
im in tears (
I believe there's a link in the thread about ota updates after rooting.
http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
---------- Post added at 02:43 AM ---------- Previous post was at 01:43 AM ----------
TrevBlu19 said:
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
Click to expand...
Click to collapse
Trying to make the other guys restore show up.... with my other phone and swapping.. trying to change timestamps...
TrevBlu19 said:
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
---------- Post added at 02:43 AM ---------- Previous post was at 01:43 AM ----------
Trying to make the other guys restore show up.... with my other phone and swapping.. trying to change timestamps...
Click to expand...
Click to collapse
Tell us which backup you used and exactly what the path is to where you put it on the phone. Is it in TWRP/BACKUPS? If so, give us the rest of the path. If TWRP's Restore menu is not showing the backup you put on the phone, it's probably (assuming it's there and in the right place) because the folder name that starts with "4" isn't the right one or because it's in the wrong place. If you haven't already done this, from TWRP, make a system image backup. You probably won't use it, but it'll create the directory in which you can put the backup from XDA. It'll have a name that your installation of TWRP can recognize. Then, you can put that unrecognized backup there and it should be seen.
I can't even get into TWRP mode now it reboots too fast now..
maigre said:
Tell us which backup you used and exactly what the path is to where you put it on the phone. Is it in TWRP/BACKUPS? If so, give us the rest of the path. If TWRP's Restore menu is not showing the backup you put on the phone, it's probably (assuming it's there and in the right place) because the folder name that starts with "4" isn't the right one or because it's in the wrong place. If you haven't already done this, from TWRP, make a system image backup. You probably won't use it, but it'll create the directory in which you can put the backup from XDA. It'll have a name that your installation of TWRP can recognize. Then, you can put that unrecognized backup there and it should be seen.
Click to expand...
Click to collapse
You mean it's looping every few seconds? What happens, exactly? Do you get the black logo screen briefly, then it all goes black and comes back again?
Maybe it's worth copying a command like
Code:
adb reboot-bootloader
or, maybe better,
Code:
fastboot reboot bootloader
so that you have it in your clipboard. Then, keep entering them into the command line. You're bound to time it right at some point, at least if it can possibly be done in the state your device is in. You might have to do:
Code:
fastboot -i 0x1bbb reboot-bootloader
If you can get into the bootloader, you should be able to get booted into TWRP from there. Keep in mind that when you do get booted into the bootloader, it won't look like anything distinct. It's just that same black logo screen you see every time you boot up (or loop, probably).
I soft-bricked my 6045i after editing the build.prop and didn't have a backup like a fool. I cannot get the phone to boot at all, stuck on the Alcatel Onetouch boot logo and can't go any further. I have tried to create an update.zip to be able to flash the build.prop thru stock recovery but so far no luck. Each time it would give me an error saying invalid footer, I tried editing the updater-script to match the device but still the error remains and I cannot sideload the update.zip.
Would it be possible for someone to upload a signed update.zip for the 6045i model with only the build.prop for use with adb sideload in stock recovery?
datkevjames said:
I soft-bricked my 6045i after editing the build.prop and didn't have a backup like a fool. I cannot get the phone to boot at all, stuck on the Alcatel Onetouch boot logo and can't go any further. I have tried to create an update.zip to be able to flash the build.prop thru stock recovery but so far no luck. Each time it would give me an error saying invalid footer, I tried editing the updater-script to match the device but still the error remains and I cannot sideload the update.zip.
Would it be possible for someone to upload a signed update.zip for the 6045i model with only the build.prop for use with adb sideload in stock recovery?
Click to expand...
Click to collapse
Flash a stock system rom image from here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745/
Important points: A corrupted build.prop should still mean you have adb access to your phone even though it won't finish booting...you can do an "adb reboot bootloader" then fastboot boot twrp and flash one of the stock recoveries.
How do I know this so well? I soft bricked mine for a day by editing the build.prop before TWRP was available.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
maigre said:
You mean it's looping every few seconds? What happens, exactly? Do you get the black logo screen briefly, then it all goes black and comes back again?
Maybe it's worth copying a command like
Code:
adb reboot-bootloader
or, maybe better,
Code:
fastboot reboot bootloader
so that you have it in your clipboard. Then, keep entering them into the command line. You're bound to time it right at some point, at least if it can possibly be done in the state your device is in. You might have to do:
Code:
fastboot -i 0x1bbb reboot-bootloader
If you can get into the bootloader, you should be able to get booted into TWRP from there. Keep in mind that when you do get booted into the bootloader, it won't look like anything distinct. It's just that same black logo screen you see every time you boot up (or loop, probably).
Click to expand...
Click to collapse
If you can execute fastboot commands, your already in bootloader.
famewolf said:
Flash a stock system rom image from here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745/
Important points: A corrupted build.prop should still mean you have adb access to your phone even though it won't finish booting...you can do an "adb reboot bootloader" then fastboot boot twrp and flash one of the stock recoveries.
How do I know this so well? I soft bricked mine for a day by editing the build.prop before TWRP was available.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
If you can execute fastboot commands, your already in bootloader.
Click to expand...
Click to collapse
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
I either need to flash an update.zip with build.prop or somehow flash an entire image uploaded to the other thread which I'm well aware of.
PS: I've tried all different sorts of adb/fastboot executables as well as multiple adb drivers (Samsung, Motorola, Google etc) even the Alcatel ones provided with their Mobile Upgrade Q app which install more of the phone than any other drivers, I've noticed.
PPS: A handful of times I was able to get a tiny bit further in stock recovery adb sideload mode, of course it was an error: 'you must use adb 1.0.32 to be able to sideload' blah blah and I made sure I was using that version.
PPPS: Is there a 3rd party app I can use to flash the image like odin or rsd lite? I cannot for the life of me get to fastboot to flash the image. Adb devices detects the phone but beyond this I can't do squat.
PPPPS: Phone is rooted and bootloader unlocked. USB debugging enabled iirc although this may be the reason for all the 'error: closed' issues.
Please someone upload a signed flashable zip with build.prop in it for 6045i (USA) model. I love this phone more than my Moto X 2014 (XT1097), that's saying something considering the Moto has more power and smoothness to it.
twrp bootloop
im able to boot into bootloader and also able to get into twrp, but cant fully reboot. i have 6045i and if anybody has any solution to this, i would greatly appreciate it.
datkevjames said:
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
I either need to flash an update.zip with build.prop or somehow flash an entire image uploaded to the other thread which I'm well aware of.
PS: I've tried all different sorts of adb/fastboot executables as well as multiple adb drivers (Samsung, Motorola, Google etc) even the Alcatel ones provided with their Mobile Upgrade Q app which install more of the phone than any other drivers, I've noticed.
PPS: A handful of times I was able to get a tiny bit further in stock recovery adb sideload mode, of course it was an error: 'you must use adb 1.0.32 to be able to sideload' blah blah and I made sure I was using that version.
PPPS: Is there a 3rd party app I can use to flash the image like odin or rsd lite? I cannot for the life of me get to fastboot to flash the image. Adb devices detects the phone but beyond this I can't do squat.
PPPPS: Phone is rooted and bootloader unlocked. USB debugging enabled iirc although this may be the reason for all the 'error: closed' issues.
Please someone upload a signed flashable zip with build.prop in it for 6045i (USA) model. I love this phone more than my Moto X 2014 (XT1097), that's saying something considering the Moto has more power and smoothness to it.
Click to expand...
Click to collapse
There are no install-script and install-binary example files to use to build a signed update.zip because there are no rom's available....maybe someone could build something using the spanish rom just posted but I don't read spanish and they seem to have built it for a 6045Y which isn't gonna help 6045i or 6045K users. If you were running twrp it wouldn't be an issue as twrp allows adb access....stock recovery doesn't..it also doesn't support rebooting to bootloader....if your bootup was "freezing" as a normal build.prop issue would then you should STILL be able to do an "adb reboot bootloader" or an "adb shell" and look around.
datkevjames said:
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
.
Click to expand...
Click to collapse
Try this:
-turn off your phone
-run command line in direcotry where is fastboot and adb.exe
-connect phone to the pc and turn the phone on
-when the phone is booting you will hear a sound that new device is detected from your pc
-in this point type "adb reboo bootloader"
-the phone should reboot to initial screen and stays there
-now you are in bootloader mode and you can flash twrp recovery
-in twrp recovery you can run file manager and copy and delete files, so you can replace the bad build.prop with your backup (you surely have)
---------- Post added at 10:58 AM ---------- Previous post was at 10:50 AM ----------
faresbreech said:
im able to boot into bootloader and also able to get into twrp, but cant fully reboot. i have 6045i and if anybody has any solution to this, i would greatly appreciate it.
Click to expand...
Click to collapse
if you have a problem then:
1- you have to tell what did you do before it happen.
anyway if you can go to TWRP, you can download system Image backup from @famewolf thread HERE, copy it to your sd card and then proceed with restore menu from TWRP. And just check the "system" .
First I rooted phone, then verified through root checker that I was truly rooted. After that I proceeded to flash twrp. Once twrp was flashed, I went to recovery to make a full backup. There I first chose read only and then backed up, but realized that I was limited on performing different actions so I reflashed twrp and this time I chose for twrp to fully work and again preformed another backup. It was when I rebooted system after the second backup when I started looping back to twrp.
I was wondering if maybe there is a terminal command I can execute through twrp to fix this like the LG G2 has. I had a problem like this before on my G2 but after executing the terminal command it would get fixed. Thanks
Sent from my Z987 using XDA Free mobile app
DallasCZ said:
Try this:
-turn off your phone
-run command line in direcotry where is fastboot and adb.exe
-connect phone to the pc and turn the phone on
-when the phone is booting you will hear a sound that new device is detected from your pc
-in this point type "adb reboo bootloader"
-the phone should reboot to initial screen and stays there
-now you are in bootloader mode and you can flash twrp recovery
-in twrp recovery you can run file manager and copy and delete files, so you can replace the bad build.prop with your backup (you surely have)
Click to expand...
Click to collapse
I tried spamming 'adb reboot-bootloader' as fast as possible, but apparently I didn't authorize my computer. ADB gives me this: error: device unauthorized. Please check the confirmation dialog on your device. ffs. Now what? I do appreciate all help. I am savvy enough to try to solve this on my own but any helpful advice would be awesome.
Can anyone please help me? I keep getting booted to TWRP.
if you can get your recovery and if your computer can download the appropriate ROM for your phone the next cos gapps downloads and raisins to your memory card and then you go to your recovery and install your ROM and gapps
apprentice
---------- Post added at 11:40 PM ---------- Previous post was at 11:38 PM ----------
you may mistakenly erased everything to me and me to past
apprentice
jairoa said:
if you can get your recovery and if your computer can download the appropriate ROM for your phone the next cos gapps downloads and raisins to your memory card and then you go to your recovery and install your ROM and gapps
apprentice
---------- Post added at 11:40 PM ---------- Previous post was at 11:38 PM ----------
you may mistakenly erased everything to me and me to past
apprentice
Click to expand...
Click to collapse
theres no roms for the h830
Markelous said:
theres no roms for the h830
Click to expand...
Click to collapse
If stuck in TWRP bootloop, just use the terminal feature in TWRP and type these commands:
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/fota
OR
Use command adb shell fix:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/fota
reboot
wolfu11 said:
If stuck in TWRP bootloop, just use the terminal feature in TWRP and type these commands:
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/fota
OR
Use command adb shell fix:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/fota
reboot
Click to expand...
Click to collapse
i get no such file or directory
Markelous said:
i get no such file or directory
Click to expand...
Click to collapse
Another option is to flash stock tot via LGup then flash the one with twrp second.
Heres a good video to follow because he hits on the importance of wiping data and rebooting twrp prior to flashing su and no-verify.
https://www.youtube.com/watch?v=9YiFOYa2L9g
wolfu11 said:
Another option is to flash stock tot via LGup then flash the one with twrp second.
Heres a good video to follow because he hits on the importance of wiping data and rebooting twrp prior to flashing su and no-verify.
https://www.youtube.com/watch?v=9YiFOYa2L9g
Click to expand...
Click to collapse
Thanks so much! ! !
I'm in the same spot, but my device is not being recognized by LGUP, so.... I'm kinda needing a system part and boot part myself. My TWRP backups were corrupted.
bedwa said:
I'm in the same spot, but my device is not being recognized by LGUP, so.... I'm kinda needing a system part and boot part myself. My TWRP backups were corrupted.
Click to expand...
Click to collapse
and it used to be recognized by LGUP right? if it wasn't I would suggest checking if your drivers are correct.
fatapia said:
and it used to be recognized by LGUP right? if it wasn't I would suggest checking if your drivers are correct.
Click to expand...
Click to collapse
I swapped between the two drivers (850 and 830) to no avail at work. Luckily I had left the LGUP open on my personal computer at home and was able to restore it when I got home... crisis narrowly avoided.
I was doing stupid experimental things anyways, so it was TOTALLY my fault.
bedwa said:
I swapped between the two drivers (850 and 830) to no avail at work. Luckily I had left the LGUP open on my personal computer at home and was able to restore it when I got home... crisis narrowly avoided.
I was doing stupid experimental things anyways, so it was TOTALLY my fault.
Click to expand...
Click to collapse
hey you recovered tho that's the important part! haha