Related
After shutting down and turning on my phone again this morning, it will not boot up and instead freezes on the white splash screen with the green HTC logo. I have tried waiting it out, clearing the caches, flashing the kernel, and just tried a hard reset, all to no avail.
Also, if I plug my phone into the charger, the orange light comes on. However, it remains on when I unplug it from the wall and the only way to get the light off is to take out the battery.
I was using a custom ROM, the Amazing QuikSense 2.1.2, for the past 4 months without any problems. I haven't installed any new applications in awhile. I don't know what caused this. What can I do to get my phone working again?
Can you get into recovery? Try taking battery out, put back in, hold volume down and power at same time and see if you can get into recovery. If so, reflash the rom.
yes, i can get into recovery and to ClockworkMod
i have already tried flashing the ROM again but it is still freezing when booting
eudemonics said:
i have already tried flashing the ROM again but it is still freezing when booting
Click to expand...
Click to collapse
How are you flashing the kernel? Fastboot or ADB? ADB may not work on a soft brick... Maybe try fastboot?
OR
Did your battery die and that's what triggered this? If your battery is dead and you are on a CWM that doesn't have charging while off, you could be screwed until u get a fresh battery. Does the phone turn off after hanging on splash screen?
Sent from my HTC_Amaze_4G using Tapatalk 2 Beta-5
i tried flashing the kernel using this utility, in ClockworkMod:
http://forum.xda-developers.com/showthread.php?t=1552889
eudemonics said:
i tried flashing the kernel using this utility, in ClockworkMod:
http://forum.xda-developers.com/showthread.php?t=1552889
Click to expand...
Click to collapse
Theres ur problem, u need to use ekf
Idk if there is still a thread with ekf, but u can just download fauxs kernel from his thread, extract the zip on your computer, put your fone in fastboot and connect the phone to the computer via usb. Open the folder u extracted the zip to and open the file that says flash.bat and it will do the rest
Sent from my NRGized Amaze...
via xda premium
i have EKF but i am using a Mac now and can't get into my PC. i used the utility because i was unable to figure out how to flash it in terminal
i have tried flashing the kernel through ADB and flashing the ROM and it is still freezing on the HTC startup screen.. i don't know what to do next.. please help
it says:
fastboot flash boot Kernel-Here/boot.img
sending 'boot' <2876 KB>... FAILED <status malformed <1 bytes>>
the boot.img file is fine - why is it failing?
im also having this problem, my phone keeps freezing at the startup screen when the htc logo pops up. i dont know much about this kind of stuff so i would really appreciated if anyone could guide me to what to do
the way that my phone froze like that was that i tried to flash a kernel for the Energy rom, i did installed the rom itself
http://forum.xda-developers.com/showthread.php?t=1362759 this is the rom that i wanted to use
and i flashed the kernel that was provided in the 4th post, i downloaded that file, extracted and ran the .bat file and thats how it happened
i would appreciate if anyone could help me with this
Urgent help me
I am using htc amaze wind
i used hasoon `s tool , i just clicked on flash your kernels and my phone is not started up. It shows me only htc screen ...
Please help me out
---------- Post added 1st November 2012 at 12:00 AM ---------- Previous post was 31st October 2012 at 11:45 PM ----------
i am new in this .. my phone is not starting up. what should i do ? when i went to team recoveries project and try to restore it shows like no os installed ..
please help me
suratimehul said:
I am using htc amaze wind
i used hasoon `s tool , i just clicked on flash your kernels and my phone is not started up. It shows me only htc screen ...
Please help me out
---------- Post added 1st November 2012 at 12:00 AM ---------- Previous post was 31st October 2012 at 11:45 PM ----------
i am new in this .. my phone is not starting up. what should i do ? when i went to team recoveries project and try to restore it shows like no os installed ..
please help me
Click to expand...
Click to collapse
I'm not sure if I can help you but other could and will if you provided more specific infos about your phone
1. What kernel did you tried to flash, using hansoon's toolkit?
2. What is your phone status before trying to flashed kernel? I.e are you rooted? Unlocked bootloader? S-Off? Running custom Rom or stock, ect and ect ...
3. When using toolkit to flash kernel, did you put ANY kernel in the "Kernels" folder at all???
antiquezip said:
I'm not sure if I can help you but other could and will if you provided more specific infos about your phone
1. What kernel did you tried to flash, using hansoon's toolkit?
2. What is your phone status before trying to flashed kernel? I.e are you rooted? Unlocked bootloader? S-Off? Running custom Rom or stock, ect and ect ...
3. When using toolkit to flash kernel, did you put ANY kernel in the "Kernels" folder at all???
Click to expand...
Click to collapse
Amaze_All-In-One_Kit_V4.0 . I UNLOCKED BOOT LOADER THAN I FLASH RECOVERY TWRP 2.3.1.0 AND I FLASHED KERNEL WITH FLASH KERNEL .. THATS ALL THAN MY PHONE DOSENT START ..
AFTER THAT I REMOVED MY BATTERY AND TRY TO PUT IN BOOTLOADER AND RUN RECOVERY , TRY TO RECOVER BUT IS SHOWS LIKE NO OS INSTALLED ??????
actually i wipe all data in recovery mode i used TWRP AND WIPE ALL SYSTEM DATA AND PHONE STORAGE .. PLEASE SOMEBODY HELP ME
---------- Post added at 02:01 PM ---------- Previous post was at 01:28 PM ----------
This will flash TWRP.
If it says "Waiting For Device"
Go to Settings -> Develop Option
and enable USB Debugging.
Press a button to continue.
C:\Users\Mehul\Desktop\Amaze_All-In-One_Kit_V4.0\data>pause
Press any key to continue . . .
C:\Users\Mehul\Desktop\Amaze_All-In-One_Kit_V4.0\data>adb kill-server
* server not running *
C:\Users\Mehul\Desktop\Amaze_All-In-One_Kit_V4.0\data>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Mehul\Desktop\Amaze_All-In-One_Kit_V4.0\data>fastboot flash recovery Re
coveries/TWRP.img
< waiting for device >
sending 'recovery' (6246 KB)... OKAY [ 1.540s]
writing 'recovery'... OKAY [ 4.535s]
finished. total time: 6.075s
C:\Users\Mehul\Desktop\Amaze_All-In-One_Kit_V4.0\data>fastboot reboot
rebooting...
finished. total time: 1.934s
C:\Users\Mehul\Desktop\Amaze_All-In-One_Kit_V4.0\data>pause
Press any key to continue . . .
You wiped all of your data and system, so it's basically means that you have nothing on your phone, no OS, nada, that's why the phone would not boot up.
I suggest you to read more before doing anything to your phone next time :fingers-crossed:
At least you still have recovery on your phone. I'm not sure if TWRP would allow your phone to be charge while off, if it's not, then you better stop doing any further and try to look around to see if you have a wall-charger to charge your battery. Make sure it's full before proceed any further.
These next steps would be
1. Read this thread
2, Flashing 4EXT recovery would be your best bet since it allow your phone to be charged while off - this will be a life saver.
3. Flash an RUU to get back to stock. Note: You will need to re-lock your bootloader in order to do this
Good luck
antiquezip said:
You wiped all of your data and system, so it's basically means that you have nothing on your phone, no OS, nada, that's why the phone would not boot up.
I suggest you to read more before doing anything to your phone next time :fingers-crossed:
At least you still have recovery on your phone. I'm not sure if TWRP would allow your phone to be charge while off, if it's not, then you better stop doing any further and try to look around to see if you have a wall-charger to charge your battery. Make sure it's full before proceed any further.
These next steps would be
1. Read this thread
2, Flashing 4EXT recovery would be your best bet since it allow your phone to be charged while off - this will be a life saver.
3. Flash an RUU to get back to stock. Note: You will need to re-lock your bootloader in order to do this
Good luck
Click to expand...
Click to collapse
thank you very much , but what should i do first i am afraid to do... please suggest me first step and be easy on me !!
You still be able to boot into your recovery, right? I don't use TWRP so I'm not sure but you will need to know how much juice you still have before going further. In 4EXT recovery, it tell you that information inside recovery though ...
Next, I would flash 4EXT recovery to make sure you can charge your phone while it's off ... using Hansoon's toolkit. Don't try to flash kernel again for you don't needed it as yet
The rest is very much already told. You will try to go back to stock by reading the link that I've provided.
PS: DON'T be affraid. DONT Panic. Just read through the Amaze Bible to gain more knowledge and confident. You'll be okay. Just take your time to read. It's not that hard as you though while in panic mode
antiquezip said:
You still be able to boot into your recovery, right? I don't use TWRP so I'm not sure but you will need to know how much juice you still have before going further. In 4EXT recovery, it tell you that information inside recovery though ...
Next, I would flash 4EXT recovery to make sure you can charge your phone while it's off ... using Hansoon's toolkit. Don't try to flash kernel again for you don't needed it as yet
The rest is very much already told. You will try to go back to stock by reading the link that I've provided.
PS: DON'T be affraid. DONT Panic. Just read through the Amaze Bible to gain more knowledge and confident. You'll be okay. Just take your time to read. It's not that hard as you though while in panic mode
Click to expand...
Click to collapse
thank you very much . yes i am still able to boot in recovery- (4EXT TOUCH ) let me go through the reading but i don't have external sd card ..IS IT FINE ??
---------- Post added at 10:05 PM ---------- Previous post was at 09:54 PM ----------
Now to the steps.
1. Download the stock ruu from here
2. Lock your bootloader by using the fastboot command "fastboot oem lock"
3. Reboot to system
4. Flash the stock RUU you downloaded by placing it in the root of your external sd card and renaming it PH85IMG.zip and rebooting to bootloader.
5. Once you have the stock rom reinstalled, set the security lock by using fastboot command " fastboot oem writesecureflag 3"
6. Profit?
I DOWNLOADED STOCK RUU ,AND I LOCKED BOOTLOADER . I REBOOT THE SYSTEM AND IT RELOCKED . NOW MOVING TO (4) STEP I DIDNT GET WHAT TO DO ???
suratimehul said:
thank you very much . yes i am still able to boot in recovery- (4EXT TOUCH ) let me go through the reading but i don't have external sd card ..IS IT FINE ??
---------- Post added at 10:05 PM ---------- Previous post was at 09:54 PM ----------
Now to the steps.
1. Download the stock ruu from here
2. Lock your bootloader by using the fastboot command "fastboot oem lock"
3. Reboot to system
4. Flash the stock RUU you downloaded by placing it in the root of your external sd card and renaming it PH85IMG.zip and rebooting to bootloader.
5. Once you have the stock rom reinstalled, set the security lock by using fastboot command " fastboot oem writesecureflag 3"
6. Profit?
I DOWNLOADED STOCK RUU ,AND I LOCKED BOOTLOADER . I REBOOT THE SYSTEM AND IT RELOCKED . NOW MOVING TO (4) STEP I DIDNT GET WHAT TO DO ???
Click to expand...
Click to collapse
Writesecurityflag??? Its been a while for me but that doesnt sound right. If s=off u want... u need the wire trick... After step 4 (which is accurate btw) u need to put the recovery.img of your choice (4ext highly recommended) in the same folder as your fastboot.exe program on pc. I recommend renaming it "recovery.img" and then you type "fastboot flash recovery recovery.img" to flash ur custom recovery of choice. From there, reboot into recovery and flash superuser.zip. then u r rooted stock
Sent from my Wicked Galaxy S III
So I did everything I could. None of the instructions on this forum help me, I am almost a complete newb in this.
I used this instruction: wiki.cyanogenmod.org/w/Install_CM_for_p3
To the part where you need to boot into recovery by holding power and volume up. Well, guess what, nothing happens when you hold power + volume up.
Please, could someone write a good step-by-step newb-friendly manual on how to get the Jelly Bean on this tab? I am seriously considering throwing this thing out of the window right now as I spent the whole evening trying to get this working with no results.
By the way, after doing all the manipulations with odin, now when the tab is loading and it shows the logo "samsung galaxy tab 10.1v", there is an image of an open lock in the bottom of the screen.
oh_delay said:
By the way, after doing all the manipulations with odin, now when the tab is loading and it shows the logo "samsung galaxy tab 10.1v", there is an image of an open lock in the bottom of the screen.
Click to expand...
Click to collapse
That means the bootloader is unlocked, the first step to install custom ROMs and recovery images.
---------- Post added at 01:18 PM ---------- Previous post was at 01:00 PM ----------
oh_delay said:
So I did everything I could. None of the instructions on this forum help me, I am almost a complete newb in this.
I used this instruction: wiki.cyanogenmod.org/w/Install_CM_for_p3
To the part where you need to boot into recovery by holding power and volume up. Well, guess what, nothing happens when you hold power + volume up.
Click to expand...
Click to collapse
Yes, with the P3, never could use POWER+VOL UP to boot into recovery (that combination can get out of stock recovery and into normal boot, which IS useful, since sometimes, one makes a mistake and stays stranded on a recovery bootloop.
Unfortunately, contrary to P4, there is no menu in the bootloader to boot into recovery.
You can however substitute that step 3 with this:
"From a terminal run adb reboot recovery"
[NOTE: its skipped in the tutorial, but for adb to function while in normal mode, you need to activate it, by going to Settings->Programmer Tools (or something like that, activate it, since its off by default and set the DEBUG USB connection on , or something - sorry, they changed the place in 4.1 and cannot give you the correct path)]
The device will then reboot into the Clockworkmod Recovery (assuming it has been correctly flashed); if not, repeat step 9 from section above.
Afterwards, you can either use adb or the Boot into Recovery menu option from the Shutdown dialog of ClockworkMod to boot into recovery.
AW: Recovery doesn't boot! Help!allready
Slow down
Bootloader unlocked ??
Custom revovery allreadY flashed??
You started With a stock Rom ??
3.1? 4.0.3?
A bit more info pls
Boot in bootloader by Holding power and volume -
Than
Fastboot flash recovery recovery.img
fastboot reboot recovery
You are still able to boot in Rom ??
Gesendet von meinem HTC One X mit Tapatalk 2
feraay said:
Slow down
Bootloader unlocked ??
Custom revovery allreadY flashed??
You started With a stock Rom ??
3.1? 4.0.3?
A bit more info pls
Click to expand...
Click to collapse
Well, yeah, apparently. I have stock 4.0.4 installed.
feraay said:
Boot in bootloader by Holding power and volume -
Than
Fastboot flash recovery recovery.img
fastboot reboot recovery
You are still able to boot in Rom ??
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
What exactly should I do? IDK what that means, "Fastboot flash recovery recovery.img
fastboot reboot recovery".
As I said, I am almost a complete newb in this.
pruano said:
That means the bootloader is unlocked, the first step to install custom ROMs and recovery images.
---------- Post added at 01:18 PM ---------- Previous post was at 01:00 PM ----------
Yes, with the P3, never could use POWER+VOL UP to boot into recovery (that combination can get out of stock recovery and into normal boot, which IS useful, since sometimes, one makes a mistake and stays stranded on a recovery bootloop.
Unfortunately, contrary to P4, there is no menu in the bootloader to boot into recovery.
You can however substitute that step 3 with this:
"From a terminal run adb reboot recovery"
[NOTE: its skipped in the tutorial, but for adb to function while in normal mode, you need to activate it, by going to Settings->Programmer Tools (or something like that, activate it, since its off by default and set the DEBUG USB connection on , or something - sorry, they changed the place in 4.1 and cannot give you the correct path)]
The device will then reboot into the Clockworkmod Recovery (assuming it has been correctly flashed); if not, repeat step 9 from section above.
Afterwards, you can either use adb or the Boot into Recovery menu option from the Shutdown dialog of ClockworkMod to boot into recovery.
Click to expand...
Click to collapse
I did adb reboot recovery, and it booted the stock recovery. Maybe I should use another recovery image? I used the one linked in the CM's instructions.
Ok, so basically what happens now is I flash recovery.tar.md5 through Odin, then it reboots in OS and I reboot it to recovery through terminal. The recovery says 'Android system recovery <3e>', so I assume it's the stock one?
feraay said:
Boot in bootloader by Holding power and volume -
Than
Fastboot flash recovery recovery.img
fastboot reboot recovery
Click to expand...
Click to collapse
Ok i figured out how to use fastboot command. Still I don't understand, which recovery.img should I flash? I don't have this file, at least not in an .img format, it's format is .tar.md5
So I guess my next question is, where can I get recovery in .img format?
OK, so I figured this out.
I downloaded the recovery.img for the Galaxy Tab 10.1 from the official CWM site (NOT 10.1v, cause they don't have it for this version. It worked fine).
then I loaded in bootloader, used ./fastboot boot <path to downloaded recovery.img>, I just dragged the img to terminal window.
Through this booted recovery, I flashed the CM rom and gapps (I did this without actually flashing the recovery, mind you).
After that, I used odin in windows again to flash their recovery.tar.md5, and now finally, when I use ./adb reboot recovery it starts up with CWM.
So yeah, thank you for your posts and thoughts, you helped me figure this out.
oh_delay said:
Through this booted recovery, I flashed the CM rom and gapps (I did this without actually flashing the recovery, mind you).
Click to expand...
Click to collapse
Yes, if you use "fastboot boot [recovery image]" instead of "fastboot flash recovery [recovery image]", you can boot to a custom recovery like CWM without flashing.
oh_delay said:
After that, I used odin in windows again to flash their recovery.tar.md5, and now finally, when I use ./adb reboot recovery it starts up with CWM.
Click to expand...
Click to collapse
Fastboot only accepts .img files, Odin only accepts tar.md5 files; however, tar.md5 files are just archive files, if you rename the file to remove the .md5 extension and use a program like 7-zip which can read .tar files, you will find one or more .img files inside, which you can extract for use with fastboot.
oh_delay said:
So yeah, thank you for your posts and thoughts, you helped me figure this out.
Click to expand...
Click to collapse
Great that you managed on your own (even with some tips), best way to learn.
---------- Post added at 12:12 PM ---------- Previous post was at 12:07 PM ----------
oh_delay said:
Well, yeah, apparently. I have stock 4.0.4 installed.
Click to expand...
Click to collapse
Its the last stock release for this tablet.
---------- Post added at 12:45 PM ---------- Previous post was at 12:12 PM ----------
oh_delay said:
I used this instruction: wiki.cyanogenmod.org/w/Install_CM_for_p3
Click to expand...
Click to collapse
One last thing: those instructions do not include adding root, as indeed you can use most of the functionality of Cyanogen without root (and possibly exposing your device to malware).
However many useful functions and apps DO require root; to check if you have root, either install this app, or do "adb shell" + "adb su", which should change the prompt from a $ to a #
For root the best way is probably to flash both zip files (ARM version) with CWM at this point (so you get the latest version); dont forget to hit the "Fix Permissions" CWM option afterwards to prevent any potential problems.
AW: Recovery doesn't boot! Help!
Noo dont take 10.1 recovery take the recovery from droidbasement.com
P3 7100 only this
And do this
Adb reboot bootloader
If not work press power and volume +
Or may
power and volume -
Should Boot into bootloader click not in download modus for Odin just take the other icon and Connect to PC
Fastboot flash recovery recovery.img
Thats all
Gesendet von meinem HTC One X mit Tapatalk 2
Sorry, not working now
Hi, I present you CWM Recovery 6.0.2.9 based on CWM from our device tree. This recovery is stable for use. In this version i fixed some bugs and added more features.
Recovery tested on: P760 (should work on every L9 with unlocked BL)
What is working:
Backup and Restore
Installing zip
ADB
All partitions are mounted
Internal SD Card fully working!
Charging
SD-EXT partition (only ext3)
Changes in the recovery from L9 CyanogenMod tree:
Fixed ADB
Added SD-EXT support
Now external_sd is default storage in recovery (internal also works)
What isn't working:
External and Internal SD USB Mount (can't be fixed because recovery don't allow to mount mtp, copy files through adb or use this app to copy: http://forum.xda-developers.com/show....php?t=1057059)
Requirements:
L9
Unlocked bootloader
Fastboot and ADB installed
Fastboot and ADB drivers
Download (1.0.0.0): Not working yet
Installation (make sure you have adb/fastboot and drivers installed):
Connect phone to computer in adb mode
Go to terminal or command line and type adb reboot oem-unlock
Now phone should be in fastboot mode
Type fastboot flash recovery path_to_downloaded_recovery_image
Booting to recovery:
Turn off phone
Turn on phone and quickly hold vol down and home button
You can also type adb reboot recovery if you are using computer or reboot recovery (before su of course) if you are using android terminal emulator
Thanks, but doesn't work for me. When i type in terminal emulator: reboot recovery, i have bootloop, now i can't use more my phone, thanks
---------- Post added at 07:24 PM ---------- Previous post was at 07:19 PM ----------
Completely bricked phone Now what is the combination for emergency mode?
---------- Post added at 07:27 PM ---------- Previous post was at 07:24 PM ----------
artas182x said:
Hi, I present you CWM Recovery 6.0.2.9 based on CWM from our device tree. This recovery is stable for use. In this version i fixed some bugs and added more features.
Recovery tested on: P760 (should work on every L9 with unlocked BL)
What is working:
Backup and Restore
Installing zip
ADB
All partitions are mounted
Internal SD Card fully working!
Charging
SD-EXT partition (only ext3)
Changes in the recovery from L9 CyanogenMod tree:
Fixed ADB
Added SD-EXT support
Now external_sd is default storage in recovery (internal also works)
What isn't working:
External and Internal SD USB Mount (can't be fixed because recovery don't allow to mount mtp, copy files through adb or use this app to copy: http://forum.xda-developers.com/show....php?t=1057059)
Requirements:
L9
Unlocked bootloader
Fastboot and ADB installed
Fastboot and ADB drivers
Download (1.0.0.0): http://www.mediafire.com/?aqa9am4tdc9rqw8
Installation (make sure you have adb/fastboot and drivers installed):
Connect phone to computer in adb mode
Go to terminal or command line and type adb reboot oem-unlock
Now phone should be in fastboot mode
Type fastboot flash recovery path_to_downloaded_recovery_image
Booting to recovery:
Turn off phone
Turn on phone and quickly hold vol down and home button
You can also type adb reboot recovery if you are using computer or reboot recovery (before su of course) if you are using android terminal emulator
Click to expand...
Click to collapse
Bricked phone completely, **** you:good:
I don't know what are you doing but for me it works, i can give you screen. To restore reflash with kdz or flash back old cwm with fastboot.
artas182x said:
I don't know what are you doing but for me it works, i can give you screen. To restore reflash with kdz or flash back old cwm with fastboot.
Click to expand...
Click to collapse
You don't understand, completely bootloop on LG screen, i can't do anything
Go to recovery using vol down + home after pressing power to turn phone.
artas182x said:
Go to recovery using vol down + home after pressing power to turn phone.
Click to expand...
Click to collapse
Doesn't work. Only bootloop. I need to enter in emergency mode to reflash all.
---------- Post added at 07:56 PM ---------- Previous post was at 07:49 PM ----------
What is combination to enter in emergency mode?
Plug in usb and press vol+. I'm also restoring phone . Sorry, tested with fastboot boot and it was working, but while using fastboot flash it don't work.
denzel09 said:
Completely bricked phone Now what is the combination for emergency mode?
Bricked phone completely, **** you:good:
Click to expand...
Click to collapse
ha ha . Now that icon does not look like thumb.
denzel09 said:
Doesn't work. Only bootloop. I need to enter in emergency mode to reflash all.
---------- Post added at 07:56 PM ---------- Previous post was at 07:49 PM ----------
What is combination to enter in emergency mode?
Click to expand...
Click to collapse
Hope you have backup of your personal data.
May be I can help, but few questions for you
1) which variant?
2) which rom you were on? which ics, which jb, or which cm?
3) why dont you people put model variant in signature? sometimes its useful for giving quick reply/solution.
I repaired normally through reflashing with kdz, but after flashing it does full wipe.
.....
Solved. Before post something, something MUST be tested. OK?
I am stuck on ics. Mo one way to reflash jelly bean, maybe unlocker bootloader can be the problem? I have try all
denzel09 said:
.....
Solved. Before post something, something MUST be tested. OK?
Click to expand...
Click to collapse
I tried to help you, but you totally ignored my post. :silly:Anyways Goodluck.
EDIT: This bootloader unlock and pushing CWM is working fine on this link
https://plus.google.com/app/basic/stream/z13pxhrrjv3sjtoe423wjzkagyveej4wa04
cmahendra said:
I tried to help you, but you totally ignored my post. :silly:Anyways Goodluck.
EDIT: This bootloader unlock and pushing CWM is working fine on this link
https://plus.google.com/app/basic/stream/z13pxhrrjv3sjtoe423wjzkagyveej4wa04
Click to expand...
Click to collapse
Oh sorry, thanks for link, i hope that i will solve to reflash jb on ics
Edit: all solved, finally.
many days my Phone dosnt work ....
I have flash Phone will not found anymour on PC . Now i have Found that it is not from ROM it is an error with this Clockwork Mod ...
This Clockwork Mod make a new File structure with fallow entrys :
/sdcard/0
i dosnt can flash stock Rom from LG , my Phone is not found from PC and my Stuff from SD Card will not found from PC.
Where can say me what for a Clockwork i can flash that make an old file Struktur !? and how i can flash it without PC ?!
Thanks for Answer and sorry for my bad english
I am realy pissed off :S
//
I dont can use fastboot, on PC say:
wait on device ....
and when i will use in terminal ....
fastboot , file not found :S
Somehow, trying to install TWRP via fastboot, I've soft bricked myself.
I can boot into fastboot mode and that's about it. My bootloader says it's still locked even though I've attempted to unlock it via the fastboot oem unlock command.
So I'm kinda stuck at the fastboot mode screen or the 1+ screen.
Any idea's?
I'm soft bricked too.
Unrooted using KingRoot and then tried to install the 2.1.3 update.
It failed and now I can't get into the system. What should I do? Can I unlock my bootloader in this state?
Try fastboot boot ( name of twrp recovery file).img
Sent from my OnePlus X
---------- Post added at 12:37 AM ---------- Previous post was at 12:35 AM ----------
Open cmd prompt in the same folder where you flashed twrp.
Sent from my OnePlus X
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
Calvin2394 said:
I'm soft bricked too.
Unrooted using KingRoot and then tried to install the 2.1.3 update.
It failed and now I can't get into the system. What should I do? Can I unlock my bootloader in this state?
Click to expand...
Click to collapse
If you didn't swipe unlock bootloader in developer settings I don't think you can. Also can you get into fastboot?
Sent from my OnePlus X
i have the same exact issue, i didn't select unlock bootloader in development settings
mawells787 said:
Try fastboot boot ( name of twrp recovery file).img
Sent from my OnePlus X
---------- Post added at 12:37 AM ---------- Previous post was at 12:35 AM ----------
Open cmd prompt in the same folder where you flashed twrp.
Sent from my OnePlus X
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
If you didn't swipe unlock bootloader in developer settings I don't think you can. Also can you get into fastboot?
Sent from my OnePlus X
Click to expand...
Click to collapse
Yep, can get into fastboot. Should I first just boot TWRP using fastboot boot, and then
1. Wipe system, 2. Install OTAs?
Edit: Unable to fastboot boot, says Device not unlocked
Edit 2: fastboot oem unlock works! Let's try flashing recovery.
The following procedure will only work if you have a microSD card with adapter for a computer. You need to download the stock rom and save it to the microSD card then place it back into the X.
Ok guys, you should still have stock recovery if twrp didn't flash. Go to this thread http://forum.xda-developers.com/showthread.php?t=3244996
Click the link to download otas, only download the one with this file name ( OnePlusOxygen_14_OTA_003_all_201510241934 ). You can flash this file through stock recovery. It should preserve your data. I personally did this while I still had a locked bootloader.
If you can't do this now, just turn the phone off and leave it charging for a while. Then just try to turn it on, or try to get into recovery.
Sent from my OnePlus X
---------- Post added at 01:03 AM ---------- Previous post was at 01:00 AM ----------
Calvin2394 said:
Yep, can get into fastboot. Should I first just boot TWRP using fastboot boot, and then
1. Wipe system, 2. Install OTAs?
Edit: Unable to fastboot boot, says Device not unlocked
Click to expand...
Click to collapse
Ok well then try to go into recovery the manual way. I believe it's power + volume up.
Sent from my OnePlus X
---------- Post added at 01:05 AM ---------- Previous post was at 01:03 AM ----------
Don't wipe anything, unless you have the stock rom readily available.
Sent from my OnePlus X
mawells787 said:
The following procedure will only work if you have a microSD card with adapter for a computer. You need to download the stock rom and save it to the microSD card then place it back into the X.
Ok guys, you should still have stock recovery if twrp didn't flash. Go to this thread http://forum.xda-developers.com/showthread.php?t=3244996
Click the link to download otas, only download the one with this file name ( OnePlusOxygen_14_OTA_003_all_201510241934 ). You can flash this file through stock recovery. It should preserve your data. I personally did this while I still had a locked bootloader.
If you can't do this now, just turn the phone off and leave it charging for a while. Then just try to turn it on, or try to get into recovery.
Sent from my OnePlus X
---------- Post added at 01:03 AM ---------- Previous post was at 01:00 AM ----------
Ok well then try to go into recovery the manual way. I believe it's power + volume up.
Sent from my OnePlus X
---------- Post added at 01:05 AM ---------- Previous post was at 01:03 AM ----------
Don't wipe anything, unless you have the stock rom readily available.
Sent from my OnePlus X
Click to expand...
Click to collapse
Sorry for bothering you, I managed to unlock my bootloader and flash recovery. I'll flash stock OTAs now and it should boot up fine.
Thank you so much for your time
How did you manage to unlock your bootloader? I cannot even get into stock recovery...It's either fastboot or nothing!
joey24z1 said:
How did you manage to unlock your bootloader? I cannot even get into stock recovery...It's either fastboot or nothing!
Click to expand...
Click to collapse
you need fastboot to unlock bootloader not recovery
Yeah, I must have tried the fastboot oem unlock command about 100 times....It just reboots and then sits on the 1+ screen......I'm stumped!
joey24z1 said:
Yeah, I must have tried the fastboot oem unlock command about 100 times....It just reboots and then sits on the 1+ screen......I'm stumped!
Click to expand...
Click to collapse
Bad news. You'll need to do a remote support session with OnePlus to have your phone reflashed with their Qualcomm tool.
Sorry for OT, didn't want to create another thread!
Here's what I did
1. Unlocked the bootloader
2. Flashed eng.stk TWRP recovery
3. Flashed OxygenOS 2.1 OTA 003
4. Flashed OxygenOS 2.1.3 OTA 004 + OTA 005
5. Rooted using SuperSU
6. Installed eng.stk blu_spark kernel
SOMEHOW, I still have my modem and IMEI partitions!
Does that mean I just need to
1. Flash stock ROM
2. Relock bootloader
To reclaim warranty?
Edit: I wiped /system before flashing OxygenOS
Calvin2394 said:
Sorry for OT, didn't want to create another thread!
Here's what I did
1. Unlocked the bootloader
2. Flashed eng.stk TWRP recovery
3. Flashed OxygenOS 2.1 OTA 003
4. Flashed OxygenOS 2.1.3 OTA 004 + OTA 005
5. Rooted using SuperSU
6. Installed eng.stk blu_spark kernel
SOMEHOW, I still have my modem and IMEI partitions!
Does that mean I just need to
1. Flash stock ROM
2. Relock bootloader
To reclaim warranty?
Edit: I wiped /system before flashing OxygenOS
Click to expand...
Click to collapse
Unlocking bootloader or installin super su doesnt voids your op warranty
mohammedtabish said:
Unlocking bootloader or installin super su doesnt voids your op warranty
Click to expand...
Click to collapse
So what does?
Usually when installing a ROM, /system needs to be wiped.
If /system wipe does not lose my IMEI partitions, I could just reflash stock ROM and my warranty is back?
Edit: Are you sure a bootloader unlock doesn't void warranty?
It was true for OPO, same goes for OPX?
Tapatalk'd from my OnePlus X
Calvin2394 said:
So what does?
Usually when installing a ROM, /system needs to be wiped.
If /system wipe does not lose my IMEI partitions, I could just reflash stock ROM and my warranty is back?
Tapatalk'd from my OnePlus X
Click to expand...
Click to collapse
If you hard brick your device or burn your cpu by overlocking or somehow
So what happens you can't unlock your boootloader? When I go into fastboot, enter fastboot oem unlock, the only thing that happens is it reboots and then gets stuck on the logo screen...Any ideas?
joey24z1 said:
So what happens you can't unlock your boootloader? When I go into fastboot, enter fastboot oem unlock, the only thing that happens is it reboots and then gets stuck on the logo screen...Any ideas?
Click to expand...
Click to collapse
Did you checked the option of oem unlocking in developers mode?
Yeah, it was unlocked before I got the bootloop
What does the following command gives ?
Code:
fastboot devices
erwann.jeanneau said:
What does the following command gives ?
Code:
fastboot devices
Click to expand...
Click to collapse
It should supply a string of numbers if your phone is connected in fastboot. If nothing comes up, the adb isn't seeing your phone.
The phone has unlockable bootloader and I only have low mobile data and was wondering if there's a way to rip the stock recovery to port twrp over.
When I get wifi tomorrow, I'll try using PC king root while the phone is in fastboot mode.
Kingoroot will get to 100 but fail, kingroot pc version would just give me Chinese letters and do nothing.
Can anyone list anyother root exploits I might I can try on this phone? I tried the Android version of kingroot , but that just gives me the request device and I can't bypass it.
Root u673c
... has anyone been able to root the U673C version 6.0.1, if so, guide me through it, thanks!
we need to somehow extract the stock recovery.img to port twrp over.
Rooted boot image for u673c
I have finally rooted this phone. Here is the rooted boot.img uploaded to MediaFire.
https://www.mediafire.com/download/r6hs4x6mju18j01
Its rooted with Magisk 17.1
Unlock bootloader rename file to boot.img and flash with fastboot.
tdawgg777 said:
I have finally rooted this phone. Here is the rooted boot.img uploaded to MediaFire.
https://www.mediafire.com/download/r6hs4x6mju18j01
Its rooted with Magisk 17.1
Unlock bootloader rename file to boot.img and flash with fastboot.
Click to expand...
Click to collapse
Awesome! SO is it possible to get more detailed instructions. It's been a few years since i've dont this stuff. My old brain's memory isn't so good.
DB225 said:
Awesome! SO is it possible to get more detailed instructions. It's been a few years since i've dont this stuff. My old brain's memory isn't so good.
Click to expand...
Click to collapse
Some instructions would be nice, Does not work I can get boot.img to install but it will only boot into stock recovery
In developer options click allow OEM unlocking then boot to fastboot mode and use fastboot to unlock bootloader and flash the rooted kernel.
Rename file to boot.img
Unlock bootloader: fastboot oem unlock
Flash kernel: fastboot flash boot boot.img
twrp is not included...
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
Here is the twrp that I used and so far seems to work fine.
https://forum.xda-developers.com/showpost.php?p=78089109&postcount=283
Thank Rortiz2 for building it.
---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------
If you are having trouble booting system after installing twrp try wiping data and cache.
The no verity zip should not be needed since kernel was patched with magisk... but if still Having issues booting system try flashing the no verity zip... you can search for it here on xda
Thank you !
I just wanted to thank you, I am disabled and dont have alot of income, This phone is my lefeline, I now have it rooted running Magisk 18.0 and TWRP is installed and seems to be working fine, However I would like to ask this. There is an pain in the ass app that seems to be part of the last firmware update this phone had, ( io.appservice.module ) ( Found in data/appi.service.module-1/base.apk
This Kunt sorry for the language, If you uninstall it it is back with every reboot ?
I can disable it to solve the problem but I would like it gone, Any thoughts ?
does anyone have twrp backup or copy firmware.I wipe internel by accident cant flash u673c no os,thanks sean
---------- Post added at 04:40 AM ---------- Previous post was at 04:32 AM ----------
does anyone have backup or copy firmware u673c cause screwed up wiped internel memory,sean
derwoodbones said:
I just wanted to thank you, I am disabled and dont have alot of income, This phone is my lefeline, I now have it rooted running Magisk 18.0 and TWRP is installed and seems to be working fine, However I would like to ask this. There is an pain in the ass app that seems to be part of the last firmware update this phone had, ( io.appservice.module ) ( Found in data/appi.service.module-1/base.apk
This Kunt sorry for the language, If you uninstall it it is back with every reboot ?
I can disable it to solve the problem but I would like it gone, Any thoughts ?
Click to expand...
Click to collapse
I would just disable the app... just in case there is an update for the phone in future... if you remove the app the update will fail but if its disabled you can just enable it take update and then disable it again... also disable the stock gallery and install a third party one from the playstore... the stock gallery app will through all sorts of ads at you full screen ads as well.
I used titainium backup to disable all apps I didn't want... bit you can use what ever app you want. You can disable most apps in the apps info but not all apps.
I just use the phone as a backup and don't know where it is right now but when I come accross it I'll post all the apps I disabled here.
I healthfully thank you
---------- Post added at 04:00 AM ---------- Previous post was at 03:59 AM ----------
I fully thank you
Thanks for the info!
In your post, you wrote, "then boot to fastboot mode".
Kindly explain how that is done on this phone. After spending hours, I can't figure it out.
Thanks again!
tdawgg777 said:
In developer options click allow OEM unlocking then boot to fastboot mode and use fastboot to unlock bootloader and flash the rooted kernel.
Rename file to boot.img
Unlock bootloader: fastboot oem unlock
Flash kernel: fastboot flash boot boot.img
twrp is not included...
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
Here is the twrp that I used and so far seems to work fine.
https://forum.xda-developers.com/showpost.php?p=78089109&postcount=283
Thank Rortiz2 for building it.
---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------
If you are having trouble booting system after installing twrp try wiping data and cache.
The no verity zip should not be needed since kernel was patched with magisk... but if still Having issues booting system try flashing the no verity zip... you can search for it here on xda
Click to expand...
Click to collapse
smuskat said:
Thanks for the info!
In your post, you wrote, "then boot to fastboot mode".
Kindly explain how that is done on this phone. After spending hours, I can't figure it out.
Thanks again!
Click to expand...
Click to collapse
I'm sorry I can remember the button combo... From phone off press and hold vol down and power release power and keep holding vol down... I think fast boot mode is an all black screen or it just has umx logo, can't remember exactly... when you have a fast hooky cmd window open type fastboot devices to see if your phone is connected... if it is not try holding vol up instead of vol down when turning phone on... if vol up don't work try holding both vol buttons. Before this can be done make sure usb debugging is enabled in developer options and authorize your pc when prompted... alternately after you have adb authorized you could use adb cmd "adb reboot bootloader"
If you ned help with adb/fastboot do a quick google search you will find plenty of info and instructions
I appreciate your reply.
But I need some more assistance, please:
I've rooted many devices, flashed custom ROM's, Custom recoveries, etc, but I'm completely stuck now with this phone.
I tried "Power and Vol Down"....nothing.
I tried "Power and Vol Up"...and for a split second I see the Android robot on its back...but after that split second, I'm in the stock recovery menu.
One of the stock recovery menu choices is to reboot into Bootloader. When I try that, the phone reboots; but to the best of my knowledge, does not get into Bootloader mode.
I have installed ADB on my PC. When I type "ADB devices", I see my phone listed. But when I type "adb reboot bootloader", it reboots, but not into Bootloader.
I have USB debugging enabled, I have authorized my PC, and in Developer options, I have enabled the "Unlock Bootloader" option.
My Googling results have not yielded useful info.
I'm stuck.....
I hope that someone with experience with this particular device can please tell me what I'm doing wrong.
Thank you!
tdawgg777 said:
I'm sorry I can remember the button combo... From phone off press and hold vol down and power release power and keep holding vol down... I think fast boot mode is an all black screen or it just has umx logo, can't remember exactly... when you have a fast hooky cmd window open type fastboot devices to see if your phone is connected... if it is not try holding vol up instead of vol down when turning phone on... if vol up don't work try holding both vol buttons. Before this can be done make sure usb debugging is enabled in developer options and authorize your pc when prompted... alternately after you have adb authorized you could use adb cmd "adb reboot bootloader"
If you ned help with adb/fastboot do a quick google search you will find plenty of info and instructions
Click to expand...
Click to collapse
hope it helps
for me command "Fastboot Continue" would make it continue to load, it did take a while....
if it continues the loop then something went wrong. as i got the infinite bootscreen 1st try.
i just reinstalled the boot image a 2nd time and it worked here's the CRC-32 Hash "a483081b"
Not sure what you mean. You wrote " command "Fastboot Continue" would make it continue to load" Do you mean from the PC command prompt? Do you mean from the phone's recovery menu?
You also wrote " i got the infinite bootscreen 1st try"
I don't know what you mean by "infinite bootscreen"......
Sorry I'm having trouble....ty!
Liberator Elite said:
for me command "Fastboot Continue" would make it continue to load, it did take a while....
if it continues the loop then something went wrong. as i got the infinite bootscreen 1st try.
i just reinstalled the boot image a 2nd time and it worked here's the CRC-32 Hash "a483081b"
Click to expand...
Click to collapse
More Info
smuskat said:
Not sure what you mean. You wrote " command "Fastboot Continue" would make it continue to load" Do you mean from the PC command prompt? Do you mean from the phone's recovery menu?
You also wrote " i got the infinite bootscreen 1st try"
I don't know what you mean by "infinite bootscreen"......
Sorry I'm having trouble....ty!
Click to expand...
Click to collapse
Sent ya PM
Smuskat
Hope That Helps.
I Got Magisk, Xposed & Even A Custom Bootscreen With Sound on Mine.
Okay. Got it all done, mostly thanks to Liberator Elite. And just so that no one else should ever be as stuck as I was, please allow me to clarify what actually worked:
I kept on attempting to put the phone into Fastboot mode or Bootloader mode. I could enter the stock recovery, choose to boot into Bootloader, but it wasn't working--or so I thought. All I would see upon reboot was a screen that was black, with the words "UMX" (Ultimate Mobile Xperience??? or whatever...)
However, Liberator Elite called to my attention that that screen WAS THE BOOTLOADER screen. I typed "Fastboot Devices" from the command prompt, and there was my phone! I then was able to flash over the boot.img file, and the TWRP posted here, and from TWRP, I was able to install Magisk.
For some of you, this is all simple--thanks for not laughing.
And to the entire community, thanks for being such a great resource! All done--thanks to you guys. Much appreciated!!!