Database Info

[Q] Help needed, Stuck in bootloop :(

Hi guys, after some helpppp
I unlocked my phone and installed TWRP, then i went to copy Superuser files to my phone, The internal memory had no folders in it whatsoever...
I rebooted the phone and still nothing so i used the "out of box restore" function from the Kwonggers toolkit, now im just stuck in bootloop
any ideas?
Thanks Craig

craig14 said:
Hi guys, after some helpppp
I unlocked my phone and installed TWRP, then i went to copy Superuser files to my phone, The internal memory had no folders in it whatsoever...
I rebooted the phone and still nothing so i used the "out of box restore" function from the Kwonggers toolkit, now im just stuck in bootloop
any ideas?
Thanks Craig
Click to expand...
Click to collapse
same issue here!!! can someone please tell me how to restore my nexus 5 without the toolkits? would appreciate it alot!!

Hoping someone has a quick fix to this! I can get into bootloader so there must still be hope? :')

here
craig14 said:
Hi guys, after some helpppp
I unlocked my phone and installed TWRP, then i went to copy Superuser files to my phone, The internal memory had no folders in it whatsoever...
I rebooted the phone and still nothing so i used the "out of box restore" function from the Kwonggers toolkit, now im just stuck in bootloop
any ideas?
Thanks Craig
Click to expand...
Click to collapse
i used Kwonggers toolkit and found several errors and bugs annoying which of them either critical or not.

Have you done a factory/data reset in recovery? That'll usually get you past a boot loop

jd1639 said:
Have you done a factory/data reset in recovery? That'll usually get you past a boot loop
Click to expand...
Click to collapse
When i try and factory reset in recovery it says it cant mount to anything!

fastboot flash userdata
if you unlock your phone, you should let the system boot up once before you flash twrp/cwm. it rebuilds the directory structure.

craig14 said:
When i try and factory reset in recovery it says it cant mount to anything!
Click to expand...
Click to collapse
If it were me, I'd flash the factory image and start over. Never did like tool kits that do every thing for you.

craig14 said:
Hi guys, after some helpppp
I unlocked my phone and installed TWRP, then i went to copy Superuser files to my phone, The internal memory had no folders in it whatsoever...
I rebooted the phone and still nothing so i used the "out of box restore" function from the Kwonggers toolkit, now im just stuck in bootloop
any ideas?
Thanks Craig
Click to expand...
Click to collapse
Flash a stock image to take phone back to stock.
Then fastboot oem unlock for bootloader
let the phone load up once, then do fastboot flash recovery xxxx.img
As for right now when you're in bootloader, try flashing stock recovery or FDR like another user said.

craig14 said:
Hi guys, after some helpppp
I unlocked my phone and installed TWRP, then i went to copy Superuser files to my phone, The internal memory had no folders in it whatsoever...
I rebooted the phone and still nothing so i used the "out of box restore" function from the Kwonggers toolkit, now im just stuck in bootloop
any ideas?
Thanks Craig
Click to expand...
Click to collapse
Download the factory image from here https://developers.google.com/android/nexus/images#hammerhead and flash it.

I cant flash anything because i cant copy any files to the phone, nothing will mount! :'(

craig14 said:
I cant flash anything because i cant copy any files to the phone, nothing will mount! :'(
Click to expand...
Click to collapse
You don't have to copy anything to your phone. Google how to set up adb / fastboot on your computer. Once set up run the fastboot flash userdata from a command prompt that the other user suggested, sorry on don't remember his name (edit, Zepius). Do you have usb debugging on?

Still bootlooping after flash
Hi,
I have the same issue so I downloaded the factory image on the website then I tried to do these steps :
Code:
- fastboot erase boot
- fastboot erase cache
- fastboot erase recovery
- fastboot erase system
- fastboot erase userdata
- fastboot flash bootloader bootloader-hammerhead.img
- fastboot reboot-bootloader
[ Wait ]
- fastboot -w update rom-hammerhead.zip
(File names might be differents)
But now I still have a bootloop then I tried to acces to recovery mode but I can't mount /sdcard :crying:

Don't just erase. Flash relevant partitions, you phone will return to stock and boot loop will be gone.

Thank's but I don't know which command I have to type
I think it's this one but I'm not sure
Code:
flash <partition> [ <filename> ] write a file to a flash partition
Could you write the command please
---------- Post added at 10:42 PM ---------- Previous post was at 10:33 PM ----------
Petrovski80 said:
Don't just erase. Flash relevant partitions, you phone will return to stock and boot loop will be gone.
Click to expand...
Click to collapse
Thank's but I don't know what I have to type exactly :/
Could you tell me ?

Alex01723 said:
Thank's but I don't know which command I have to type
I think it's this one but I'm not sure
Code:
flash <partition> [ <filename> ] write a file to a flash partition
Could you write the command please
---------- Post added at 10:42 PM ---------- Previous post was at 10:33 PM ----------
Thank's but I don't know what I have to type exactly :/
Could you tell me ?
Click to expand...
Click to collapse
You need to read this: http://forum.xda-developers.com/showthread.php?t=2513701
Use method 2. I'm not sure about the scrips, haven't used those.

Petrovski80 said:
You need to read this: http://forum.xda-developers.com/showthread.php?t=2513701
Use method 2. I'm not sure about the scrips, haven't used those.
Click to expand...
Click to collapse
I LOVE YOU, i am forever in your debt

Problem Solved
Petrovski80 said:
You need to read this: http://forum.xda-developers.com/showthread.php?t=2513701
Use method 2. I'm not sure about the scrips, haven't used those.
Click to expand...
Click to collapse
Love you too you solved the problem thank's a lot

Petrovski80 said:
You need to read this: http://forum.xda-developers.com/showthread.php?t=2513701
Use method 2. I'm not sure about the scrips, haven't used those.
Click to expand...
Click to collapse
Heyy man, half a year later and Ill still thank you for this.. Totally saved my bricked Nexus 5.. Thank you Thank you... I can now sleep well tonight. :good:

[Q] USB device not recognized

Gday,
I did many searches and I read the " here are the similar treads found" but none has the solution. I am reading and searching for the last 3 hours, but no sigar. SO I am hoping someone can help me out.
I used this link to install my current ROM - http://forum.xda-developers.com/showthread.php?t=2445392
HTC one 2 ville
ROM maximus 10
I had TWRP 2.6.3 installed
All was working fine, only to have TWRP working with this ROM I needed to use TWRP 2.6.1. As I was not able to run backups.
So I went into fastboot USB. Run the below command.
C:\HTC>fastboot flash recovery recovery.img
sending 'recovery' (6246 KB)...
OKAY [ 1.009s]
writing 'recovery'...
OKAY [ 1.501s]
finished. total time: 2.510s
And after this I guess I screwed up something.
The laptop is not recognizing the phone anymore and says the device is malfunctioned.
I cannot get in TWRP recovery anymore. If I try the screen goes black. I need to hold the power button to turn it off.
WinDROID is not seeing the device either
I just cleared cache, dalvik, wiped data and went back to factory default.
That did not helped a thingy.
USB settings:
If I change it to HTC sync manager of clear check mark either way it comes with the same message " USB not recognized".
Can someone help me out plz
Thanks a lot

I reinstalled HTC drivers and now the phone gets recognized again.
But I still cannot install anything from recovery....
E:\Can't mount /sdcard/

After I installed the HTC drivers I was able to get on the sdcard again and get connected.
I installed TWRP 2.6.3. and I am able to boot in recovery,
That's nice, but now TWRP say's I only have 48MB on the SDcard?? When booted in systeem and connected to my laptop it tells me the SDcard = 11.9GB and has 11.6GB free.....
At least the phone keeps me off the street

INstalled SDrescan. That does not solve it.
Also TWRP 2.6.3 gives different info. Like battery 66% and on another page it tells me it has 100%.
Does this means the SDcard is damaged?

Ray187 said:
INstalled SDrescan. That does not solve it.
Also TWRP 2.6.3 gives different info. Like battery 66% and on another page it tells me it has 100%.
Does this means the SDcard is damaged?
Click to expand...
Click to collapse
you need to flash the stock recovery, then go to bootloader and perform "factory reset + clear storage".
nce done you can flash your custom recovery again and you should be fine

Thanks.
I have hboot 2.16. I thought that there is no stock Rom for this hboot. I,ll have a look.

Ray187 said:
Thanks.
I have hboot 2.16. I thought that there is no stock Rom for this hboot. I,ll have a look.
Click to expand...
Click to collapse
HBoot 2.16 means you're "S-OFF" and can run ANY RUU

LS.xD said:
HBoot 2.16 means you're "S-OFF" and can run ANY RUU
Click to expand...
Click to collapse
Yes..after I read your post I slapped myself.....twice

HHmmzz
I copied the RUU to the root om the SDcard. Then I rebooted into recovery. Recovery is not able to see the root of the SDcard. Only folders he can see are TWRP and CWM.
Now I cannot even get on fastboot USB anymore. When I reboot the device the screen is blinking green.
*edit*
I mounted the USB device so it popped up on my laptop. And here as well it says it has only 48MB. SO no chance to copy the RUU.
Is there another way to flash my phone?

What did you do? The RUU needs to be started in Windows
Sent from my beloved HTC One S using (most time buggy) Tapatalk
---------- Post added at 10:11 AM ---------- Previous post was at 09:58 AM ----------
Ray187 said:
HHmmzz
I copied the RUU to the root om the SDcard. Then I rebooted into recovery. Recovery is not able to see the root of the SDcard. Only folders he can see are TWRP and CWM.
Now I cannot even get on fastboot USB anymore. When I reboot the device the screen is blinking green.
*edit*
I mounted the USB device so it popped up on my laptop. And here as well it says it has only 48MB. SO no chance to copy the RUU.
Is there another way to flash my phone?
Click to expand...
Click to collapse
Did you reed anything about using RUU? Connect phone in fastboot mode and run the RUU in windows. You need to flash stock recovery and set your CID back to stock before you can use the RUU.

LS.xD said:
What did you do? The RUU needs to be started in Windows
Sent from my beloved HTC One S using (most time buggy) Tapatalk
---------- Post added at 10:11 AM ---------- Previous post was at 09:58 AM ----------
Did you reed anything about using RUU? Connect phone in fastboot mode and run the RUU in windows. You need to flash stock recovery and set your CID back to stock before you can use the RUU.
Click to expand...
Click to collapse
I used to install RUU it on my previous phone. I cannot get fastboot USB connected anymore. I can't get the phone connected to my laptop at all. gives me the device malfuntion.
Bit frustrated...I almost broke the phone in half :laugh:
For now I just keep using it with the current ROM. Maximus 4.2.2 and sence 5.0 S-off. I did not changed CID.
I will try again in a couple of days.
Thank you :good:

nvm

Owkeee smie again
Couldn't recist trying to fix this.
I managed to get fastboot USB active. So I tried to erase recovery. That failed as remote is not allowed. Then I flash TWRP 2.6.1.0 succesfully.
And now it's back to normal.
2 bad I damaged the phone a bit. I forgot the one s is a phone you cannot open to remove the battery of SDcard....thought about it while having a screwdriver in my hand and partly in the phone :silly:
Appriciated your replies LSxD :good:

Ray187 said:
Owkeee smie again
Couldn't recist trying to fix this.
I managed to get fastboot USB active. So I tried to erase recovery. That failed as remote is not allowed. Then I flash TWRP 2.6.1.0 succesfully.
And now it's back to normal.
2 bad I damaged the phone a bit. I forgot the one s is a phone you cannot open to remove the battery of SDcard....thought about it while having a screwdriver in my hand and partly in the phone :silly:
Appriciated your replies LSxD :good:
Click to expand...
Click to collapse
Means your phone is working again? Or did you kill it with the screwdriver?

LS.xD said:
Means your phone is working again? Or did you kill it with the screwdriver?
Click to expand...
Click to collapse
Phone works fine again. Able to connect it to the PC, use fastboot and get in recovery and see full size SDcard :good:
So will be making a backup and copy those files to my NAS.
I damaged the phone a bit physically at the back.

[Q] Stuck on black screen

Need help! I recently bought a sim-free Moto G in Germany (I'm from Argentina).
I unlocked the bootloader and when I booted up, I got a lot of messages sayng that procesess had stopped. At first it started with systemui, then phone.android, then system and so on. Then I decided to try to reboot the phone. When I turned it on, it didn't get to the system, it just stayed on a black screen...:crying:
Update: It doesn't even finish the boot animation, and then it goes to a black screen
Fix: flash custom recovery, fix permissons, wipe cache and dalvik cache then installstock software through bootloader

LittleConfucy said:
Need help! I recently bought a sim-free Moto G in Germany (I'm from Argentina).
I unlocked the bootloader and when I booted up, I got a lot of messages sayng that procesess had stopped. At first it started with systemui, then phone.android, then system and so on. Then I decided to try to reboot the phone. When I turned it on, it didn't get to the system, it just stayed on a black screen...:crying:
Update: It doesn't even finish the boot animation, and then it goes to a black screen
Click to expand...
Click to collapse
Restore Stock ROM with Fastboot

Please tell me how!!!!! I don't even know if it is charging anymore...
Is it done by going to recovery and selecting the "Factory option"?

If it's done that way, I have already tried ?

Anyone elsae have any ideas how to fix this?:fingers-crossed:
Maybe re-locking the bootloader?

Its not broken if you can enter fasboot (volume down and power) you can see if your phone charges or not as well
Sent from my XT1032 using XDA Free mobile app

Clarkiieh said:
Its not broken if you can enter fasboot (volume down and power) you can see if your phone charges or not as well
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
It is charging, luckily. Another thing I forgot to metion: when I turn it off it turns on again automatically (It can't stay turned off)
Also, I can enter fastboot and the computer does detect it wh I connect it

LittleConfucy said:
It is charging, luckily. Another thing I forgot to metion: when I turn it off it turns on again automatically (It can't stay turned off)
Also, I can enter fastboot and the computer does detect it wh I connect it
Click to expand...
Click to collapse
I had same issue... You need to do the following because your system images are not flashing.
What was your Previous ROM/Stock Firmware?
If you can enter fastboot and your computer detects it.. Good.
Redownload a STOCK firmware.
Now extract it to a new folder to use desktop.
Copy and past the mfastboot files into where you have extracted..
Now mfastboot flash them one by one.
Now you need to use your brain and not follow everyone else's posts because inside the extracted firmware the files can be written wrong to what your copy and pasting.
For instance I was trying the following.
" mfastboot flash system system.IMG"
This gave me sparse chunk error
Or
"Mfastboot flash system system.img sparse chunk1"
Wouldn't recognise the command
Neither worked because inside the firmware it was broken into 3 sparse chunks
They were written as
"system sparsechunk.0"
"system sparsechunk.1"
"system sparsechunk.2"
Just check what there called and copy and paste
Sent from my XT1032 using XDA Free mobile app
---------- Post added at 03:57 AM ---------- Previous post was at 03:54 AM ----------
Clarkiieh said:
I had same issue... You need to do the following because your system images are not flashing.
What was your Previous ROM/Stock Firmware?
If you can enter fastboot and your computer detects it.. Good.
Redownload a STOCK firmware.
Now extract it to a new folder to use desktop.
Copy and past the mfastboot files into where you have extracted..
Now mfastboot flash them one by one.
Now you need to use your brain and not follow everyone else's posts because inside the extracted firmware the files can be written wrong to what your copy and pasting.
For instance I was trying the following.
" mfastboot flash system system.IMG"
This gave me sparse chunk error
Or
"Mfastboot flash system system.img sparse chunk1"
Wouldn't recognise the command
Neither worked because inside the firmware it was broken into 3 sparse chunks
They were written as
"system sparsechunk.0"
"system sparsechunk.1"
"system sparsechunk.2"
Just check what there called and copy and paste
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
This is just a guide on the common errors I was reviving ... There's a lot of guide on how to reflash stock firmware and there soon easy to do pm me if you need a compete walkthrough I've mastered it now I've corrupted my phone god knows how many times
Sent from my XT1032 using XDA Free mobile app
---------- Post added at 04:00 AM ---------- Previous post was at 03:57 AM ----------
http://forum.xda-developers.com/showthread.php?t=2542219
Follow that guide take in mind what I have just said download the lastest firmware for your region I reccomend retail if its in your region
Sent from my XT1032 using XDA Free mobile app

Clarkiieh said:
I had same issue... You need to do the following because your system images are not flashing.
What was your Previous ROM/Stock Firmware?
If you can enter fastboot and your computer detects it.. Good.
Redownload a STOCK firmware.
Now extract it to a new folder to use desktop.
Copy and past the mfastboot files into where you have extracted..
Now mfastboot flash them one by one.
Now you need to use your brain and not follow everyone else's posts because inside the extracted firmware the files can be written wrong to what your copy and pasting.
For instance I was trying the following.
" mfastboot flash system system.IMG"
This gave me sparse chunk error
Or
"Mfastboot flash system system.img sparse chunk1"
Wouldn't recognise the command
Neither worked because inside the firmware it was broken into 3 sparse chunks
They were written as
"system sparsechunk.0"
"system sparsechunk.1"
"system sparsechunk.2"
Just check what there called and copy and paste
Sent from my XT1032 using XDA Free mobile app
---------- Post added at 03:57 AM ---------- Previous post was at 03:54 AM ----------
This is just a guide on the common errors I was reviving ... There's a lot of guide on how to reflash stock firmware and there soon easy to do pm me if you need a compete walkthrough I've mastered it now I've corrupted my phone god knows how many times
Sent from my XT1032 using XDA Free mobile app
---------- Post added at 04:00 AM ---------- Previous post was at 03:57 AM ----------
http://forum.xda-developers.com/showthread.php?t=2542219
Follow that guide take in mind what I have just said download the lastest firmware for your region I reccomend retail if its in your region
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Now, at least it's booting into system, but I get two messages: "Unfortunately, process com.android.phone has stopped" "Unfortunately, the Hangaouts app has stopped"
Oh, and many many thanks... You're my saivour!!!!!
EDIT: I started getting other process stopped errors

LittleConfucy said:
Now, at least it's booting into system, but I get two messages: "Unfortunately, process com.android.phone has stopped" "Unfortunately, the Hangaouts app has stopped"
Oh, and many many thanks... You're my saivour!!!!!
EDIT: I started getting other process stopped errors
Click to expand...
Click to collapse
Try clear app cache for the apps force closing..
Or flash twrp recovery and and wipe cache and dalvik and fixing permissions in advance.
If none of them help look for 4.2.2 gapps for stock
If none of these help the only thing I can suggest it retry flashing, should be a cache issue though 9 - 10 time it is. No worry's at friend I know how annoying it can be. Did my checking what the system.IMG files where called help?
Edit if all else fails I would try downgrading to 4.3 and updating ot
Sent from my XT1032 using XDA Free mobile app

Clarkiieh said:
Try clear app cache for the apps force closing..
Or flash twrp recovery and and wipe cache and dalvik and fixing permissions in advance.
If none of them help look for 4.2.2 gapps for stock
If none of these help the only thing I can suggest it retry flashing, should be a cache issue though 9 - 10 time it is. No worry's at friend I know how annoying it can be. Did my checking what the system.IMG files where called help?
Edit if all else fails I would try downgrading to 4.3 and updating ot
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
First of all, I forgot to mention that the com.android.phone has stopped message is persistent, when I press ok, it reappears, so I cant use the system.
Also, after rebooting the screen went black again just like before, and the recovery gets stuck on the splash screen...
(God did I f*ck up!)

Okay, try reflashing stock but this time try downgrade, that might work
Or reflash what you did in the first place to get this far..
Did all the commands say OKAY after flashing?
Did you use "mfastboot clear userdata"
And cache commands?
Sent from my XT1032 using XDA Free mobile app
---------- Post added at 07:34 AM ---------- Previous post was at 07:30 AM ----------
LittleConfucy said:
First of all, I forgot to mention that the com.android.phone has stopped message is persistent, when I press ok, it reappears, so I cant use the system.
Also, after rebooting the screen went black again just like before, and the recovery gets stuck on the splash screen...
(God did I f*ck up!)
Click to expand...
Click to collapse
Reflash recovery, try doing it all in this order.
Flash Stock Firmware.
Reboot to boot loader
("mfastboot reboot reboot-bootloader")
Flash another recovery
Then reboot to recovery on fasboot menu on phone.
Sent from my XT1032 using XDA Free mobile app

Status update: Magically, the recovery started working again by itself...
Is there a way to falsh a stock ROM from recovery? Because, from what I have seen, when I install a stock image through bootloader, it boots automatically to system. The thing is, when I reboot the phone, the screen goes black again just like before :fingers-crossed:
I will repeat it a million times if necessary: YOU ARE MY SAVIOUR!!!!!!!!!!!!!!

Maybe download one, push to SD card using adb
I think the command is "adb push (file name).zip /sdcard" not sure though
Then install one over recovery
If it boots you know its a issue with the stock firmware your using
Sent from my XT1032 using XDA Free mobile app

Clarkiieh said:
Maybe download one, push to SD card using adb
I think the command is "adb push (file name).zip /sdcard" not sure though
Then install one over recovery
If it boots you know its a issue with the stock firmware your using
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
No need, I fixed permissions, wiped Cache and D. Cache, and then installed the stock software and it worked!!!!!!!!!
I really cannot thank you enough! :victory::good:
The thing is that I had an 8GB Moto G before, but someone stole it from me recently, so I would have died if I lost this one too.

Haha awesome so you wiped cache and dalkik.. Then did you reflash a stock firmware/ROM using fastboot or have you flashed using recovery?
No trouble at all, I know what its like when you need help and sometimes there isn't anyone...
Sent from my XT1032 using XDA Free mobile app

"same" problem here
i read all, and try all..
but, not work for me..
maybe you can help me now..
http://forum.xda-developers.com/showthread.php?t=2704207&page=7

Clarkiieh said:
Haha awesome so you wiped cache and dalkik.. Then did you reflash a stock firmware/ROM using fastboot or have you flashed using recovery?
No trouble at all, I know what its like when you need help and sometimes there isn't anyone...
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I flashed it throug fastboot :victory:

hansdepaula said:
"same" problem here
i read all, and try all..
but, not work for me..
maybe you can help me now..
http://forum.xda-developers.com/showthread.php?t=2704207&page=7
Click to expand...
Click to collapse
Will try to do all I can to help... :good:

[Q] Cache issue, bricked. please help me. Reward!

Hey guys and gals, I'm having a huge issue with my nexus 5. Today I used the stock recovery to clear the Cache. It looked like it had froze so like an idiot i forced the phone to restart. Now it says my cache partition is messed up and my storage isn't mounted. I also show an unknown base-band so I cant use cell service. I can however still boot my phone up and go into the bootloader screen and also boot it up normally. I looked up and attempted to fastboot the cache.img file back onto the phone, but every time I try I get an error message saying "failed : remote not supported in locked device" something or other like that in the CMD screen. My phone is stock, bootloader is locked and I do not have root or anything else on it. what do I have to do to flash this cache.img file and get my phone working again? I looked up all the info so far but I'm at a dead end. I can figure out basic things but im no genius unfortunately. I'm at the point where Ill paypal a reward to whoever helps me. Please someone help me. I en

How can you use fastboot on locked bootloader? I don't think it's possible

Try to clear the cache again.it worked for me.
Sent from my Nexus 5 using Tapatalk

geemaan said:
Try to clear the cache again.it worked for me.
did you have the same thing I have wrong? on the recovery screen when I try to clear cache I get this message
Wiping Cache
"E: failed to mount /cache (invalid argument)
formatting /cache
Should I leave it like that for awhile? the longest I have left it like that is like 5 minutes. It doesnt seem like its doing anything.
Click to expand...
Click to collapse

Unlock the bootloader and try
Sent from my Android L Nexus 5 via Tapatalk

you can just reflash the cache using fastboot. yes, you can use fastboot on any locked or unlocked device.
---------- Post added at 06:24 PM ---------- Previous post was at 06:23 PM ----------
MARKOZD15 said:
How can you use fastboot on locked bootloader? I don't think it's possible
Click to expand...
Click to collapse
how did you unlock your bootloader with fastboot when your device was locked when you used fadtboot? yea. any locked or unlocked nexus device.

Lol. I guess that makes perfect sense!
Sent from my Android L Nexus 5 via Tapatalk

[Q&A] **TWRP** custom recovery for IDOL3 6045

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.