Related
As the title states, I recently woke up to find my phone in the fast boot menu.
I have no idea what's going on or why it's in this state, as I've done nothing to it.
No root. No custom recovery. Nothing.
I simply put it down before I went to bed and that was all.
I've tried going into the 'hboot' option and selecting Fastboot, recovery, and even Factory Reset as a final option. All that happens whenever I've selected any option is that the phone reloads back into fastboot. The splash screen before hand is of 3 android mascots on skateboards.
I've seen some other threads here with similar issues, yet none like mine.
They've all seemed to be rooted phones, with or without custom recoveries on them.
I've no idea what's going on with the phone and would really appreciate any help or advice.
What is your OS number on the bootloader screen?
redpoint73 said:
What is your OS number on the bootloader screen?
Click to expand...
Click to collapse
The OS Number is 4.20.531.5
ViaJCE said:
The OS Number is 4.20.531.5
Click to expand...
Click to collapse
So if its never been modded, the bootloader screen should also say LOCKED near the top and SOFTWARE OFFICIAL (or something like that). Can you confirm those?
If so, you can try to run the RUU and see if that helps the issue. Just download the RUU to a Windows PC (Win7 and USB 2.0 for best results), connect the phone to the PC in bootloader-fastboot mode, and double-lock the RUU executable to run it. You'll also need to have HTC Sync installed on the PC.
Find the 4.20.531.5 RUU here: http://forum.xda-developers.com/showthread.php?t=2714456
redpoint73 said:
So if its never been modded, the bootloader screen should also say LOCKED near the top and SOFTWARE OFFICIAL (or something like that). Can you confirm those?
If so, you can try to run the RUU and see if that helps the issue. Just download the RUU to a Windows PC (Win7 and USB 2.0 for best results), connect the phone to the PC in bootloader-fastboot mode, and double-lock the RUU executable to run it. You'll also need to have HTC Sync installed on the PC.
Find the 4.20.531.5 RUU here: http://forum.xda-developers.com/showthread.php?t=2714456
Click to expand...
Click to collapse
Yeah, as you said, it says
*** Software status: Official ***
*** LOCKED *** (highlighted in purple) on top in the menu.
I have actually tried using the RUU software before. The times that I've tried using it, it attempts to reboot the phone back into the fastboot menu, which turns it off. The phone never turns back on in time, for as soon as it does, the software says it's unable to do it.
Though I haven't tried that double-lock method you mentioned. And I do have the HTC Sync software installed as well.
ViaJCE said:
Though I haven't tried that double-lock method you mentioned.
Click to expand...
Click to collapse
It should say "double click" (to run the RUU program). Not sure if there was some runaway spellcheck going on there, when I posted. But its not any different from what you've tried.
Another method you can try, is to download the RUU zip from Post #4 of the same thread: http://forum.xda-developers.com/showpost.php?p=51836733&postcount=4
Rename to 0P6BIMG.zip, copy to SD card, insert card into phone, and reboot into bootloader, and it should automatically install it.
redpoint73 said:
It should say "double click" (to run the RUU program). Not sure if there was some runaway spellcheck going on there, when I posted. But its not any different from what you've tried.
Another method you can try, is to download the RUU zip from Post #4 of the same thread: http://forum.xda-developers.com/showpost.php?p=51836733&postcount=4
Rename to 0P6BIMG.zip, copy to SD card, insert card into phone, and reboot into bootloader, and it should automatically install it.
Click to expand...
Click to collapse
Thanks for the replies and the help so far. I clicked on the link with the 4.20.531.4 ROM, yet it no longer seems to be there.
ViaJCE said:
Thanks for the replies and the help so far. I clicked on the link with the 4.20.531.4 ROM, yet it no longer seems to be there.
Click to expand...
Click to collapse
Search to see if it was posted elsewhere (4.20.530.4 RUU in zip format). Otherwise, another option is to run the RUU.exe on your PC, then look in your Windows temp folder for a ROM.zip, which is the same thing (zip format RUU).
redpoint73 said:
Search to see if it was posted elsewhere (4.20.530.4 RUU in zip format). Otherwise, another option is to run the RUU.exe on your PC, then look in your Windows temp folder for a ROM.zip, which is the same thing (zip format RUU).
Click to expand...
Click to collapse
Alright, so I've gotten the rom.zip from the ruu.exe.
I've renamed it as you said to, moved it to an SD card, and popped that SD card into the M8.
I turned on the M8 and it went into the fastboot menu as expected. I then selected the hboot option.
It then started to read the zip and flash it, then asking if I want to start the update.
After selecting yes, the bootloader started updating, but the partition update failed.
it read,
[1] BOOTLOADER - Fail-PU
*then after a list of 15 other items
Partition update fail!
Update Fail!
Device halted due to large image update fail!
Press <power> to reboot.
Hi,
You should unlock your bootloader and flash recovery to get it back in stock if the RUU don't work..
BelDev said:
Hi,
You should unlock your bootloader and flash recovery to get it back in stock if the RUU don't work..
Click to expand...
Click to collapse
Thanks for the suggestion, though I've already tried that. It hadn't worked. Wasn't able to do it: I forgot the error it gave me
@ViaJCE
If you got a error, verify if you have all drivers installed and if adb detect your device..
BelDev said:
Hi,
You should unlock your bootloader and flash recovery to get it back in stock if the RUU don't work..
Click to expand...
Click to collapse
This is false. Stock recovery is not needed for RUU, but it is for OTA (which RUU and OTA are two very different things).
In any case, it doesn't appear the device was ever modded (to not have the stock recovery) in the first place.
---------- Post added at 09:13 AM ---------- Previous post was at 09:08 AM ----------
ViaJCE said:
[1] BOOTLOADER - Fail-PU
*then after a list of 15 other items
Partition update fail!
Update Fail!
Device halted due to large image update fail!
Press <power> to reboot.
Click to expand...
Click to collapse
Can you post the whole install log output?
Failure to write partitions with the proper RUU (locked bootloader, stock device), plus the spontaneous OS failure that started this whole discussion, to me implies a sudden hardware failure (bad emmc, etc.) and you might be out of luck here.
*bump*
redpoint73 said:
This is false. Stock recovery is not needed for RUU, but it is for OTA (which RUU and OTA are two very different things).
In any case, it doesn't appear the device was ever modded (to not have the stock recovery) in the first place.
---------- Post added at 09:13 AM ---------- Previous post was at 09:08 AM ----------
Can you post the whole install log output?
Failure to write partitions with the proper RUU (locked bootloader, stock device), plus the spontaneous OS failure that started this whole discussion, to me implies a sudden hardware failure (bad emmc, etc.) and you might be out of luck here.
Click to expand...
Click to collapse
Posting everything the phone says when it's going through the process will be hard, but I'll try to anyways.
redpoint73 said:
This is false. Stock recovery is not needed for RUU, but it is for OTA (which RUU and OTA are two very different things).
In any case, it doesn't appear the device was ever modded (to not have the stock recovery) in the first place.
---------- Post added at 09:13 AM ---------- Previous post was at 09:08 AM ----------
Can you post the whole install log output?
Failure to write partitions with the proper RUU (locked bootloader, stock device), plus the spontaneous OS failure that started this whole discussion, to me implies a sudden hardware failure (bad emmc, etc.) and you might be out of luck here.
Click to expand...
Click to collapse
From selecting hboot on the Fastboot menu, it then says,
SD Checking
No gift file
Loading . . . [0P6BDIAG.zip]
No Image!
Loading . . . [0P6BDIAG.nbh]
No image or wrong image!
Loading . . . [0P6BDIMG.zip]
then it finishes loading, to then say 'flashing zip'
some other text flies by on the screen to fast to be read, then it says 'Checking Hboot Version . . .'
Then it says,
Parsing . . . [SD ZIP]
Reset HTC Debug Flag . . .
[ 1 ] Bootloader
[ 2 ] Splash1
[ 3 ] Trust_Zone
[ 4 ] RPM
[ 5 ] ADSP
[ 6 ] PG2FS_SPCUSTOM
[ 7 ] WCNSS
[ 8 ] TP (2)
[ 9 ] SENSOR HUB
[ 10 ] SDI
[ 11 ] SBL1 (4)
[ 12 ] Recovery
[ 13 ] Boot
[ 14 ] Radio_V2
[ 15 ] Radio_CUST
Do you want to start update?
After clicking yes, it begins to update the bootloader
[ 1 ] Bootloader - Updating
but then that fails, saying
[ 1 ] Bootloader - Fail - PU
The at the bottom of the list, it states,
Partition update fail!
Update Fail!
Device halted due to large image update fail!
Press <power> to reboot.
Unfortunately, the full output doesn't shed any additional light. Based on the collection of symptoms, I'd tend to think you have a hardware failure. Sorry . . .
redpoint73 said:
Unfortunately, the full output doesn't shed any additional light. Based on the collection of symptoms, I'd tend to think you have a hardware failure. Sorry . . .
Click to expand...
Click to collapse
Well, thank you for trying to help out anyways. I'll continue to exhaust any and all additional options I have left, as I still think that the phone can be saved. If I'm proven wrong, and there's nothing that can be done, then I'll give up.
Still got hope though
Thread sharing...so easy to find another user
Credit bala
Your complete guide for recovering from bricked HTC desire 630
I. Downloading Stock Rom
1. Download HTC Desire 630 Stock boot image from
Download link
2. Download HTC Desire 630 Stock Recovery image from
Download link
3. Download HTC Desire 630 original signed firmware from
[url]http://www.mediafire.com/file/5ifvwx...d_signed_2.zip"]Download link[/URL]
4. Download adb and fastboot files from [url]https://forum.xda-developers.com/sho....php?t=2317790[/URL] and install it.
II. Preparing to start
1. Rename the 2PSTIMG_A16_DWGL_M60_DESIRE_SENSE70GP_HTC_India_SE A_1.02.400.1_Radio_0.57.62.0506_CNV_1.47_09B_relea se_485282_combined_signed_2.zip file to just 2PSTIMG.zip (Important)
2. Remove and connect your Memory card with a Card reader (Important) in computer and copy the above file to the root of memory card. Don't insert your memory card to your device now (Important)
3. Press and hold volume down button and power on the device.
4. Select FastBoot from the boot menu in device and connect to the computer with usb cable.
5. Go to C:\Program Files (x86)\Minimal ADB and Fastboot in computer
6. press and hold shift button and right click inside the folder and select 'open command window here'
III. Flashing
1. Flash stock recovery of HTC desire 630 using the following command in the command window (example : Fastboot flash recovery
"C:\Users\admin\Downloads\recovery_signed.img" )
Fastboot flash recovery "your location " recovery_signed.img file
2. Flash stock boot using Fastboot flash boot "your location " boot_signed.img file
3. OEM Lock the device using Fastboot oem lock (Important)
4. Now Insert the memory card in your device.
5. Select Power Down in Fastboot menu in Phone
6. Press and hold Volume Down Button and Power on the device.
7. Now wait. It will flash the system to its original state. Don't reboot in middle. It will take minimum 10 mins to complete.
8. After flashing, device will ask you to reboot.
First boot after flash will take around 5mins to complete. Don't reboot in middle.
res
System image is too large to flash... My device is Europe variant..
My device is stuck at HTC boot logo... I think that system image is empty or the boot image is different than mine.. PLS help me. I'm not noob in android devices but this phone is hard to fix..
Dude, you have just copy pasted Bala's post as a new thread without giving him credit.
---------- Post added at 02:35 PM ---------- Previous post was at 02:34 PM ----------
jorimafia said:
System image is too large to flash... My device is Europe variant..
My device is stuck at HTC boot logo... I think that system image is empty or the boot image is different than mine.. PLS help me. I'm not noob in android devices but this phone is hard to fix..
Click to expand...
Click to collapse
Ignore the error and keep selecting "Yes", it will eventually flash.
dearbasheer said:
Dude, you have just copy pasted Bala's post as a new thread without giving him credit.
---------- Post added at 02:35 PM ---------- Previous post was at 02:34 PM ----------
Ignore the error and keep selecting "Yes", it will eventually flash.
Click to expand...
Click to collapse
Bro actually I didn't know who deserve proper credit but if you say he is bala so I add name
Found some stock roms for this device HERE
mr_techno said:
Found some stock roms for this device HERE
Click to expand...
Click to collapse
It is paid
jorimafia said:
It is paid
Click to expand...
Click to collapse
Subscription Plan: Free
Subscription Period: 12 Months
Extra Daily Free Downloads: 3 GB
Allowed to Change PC: 1 Time/s Monthly
Just register for a free plan.
mr_techno said:
Subscription Plan: Free
Subscription Period: 12 Months
Extra Daily Free Downloads: 3 GB
Allowed to Change PC: 1 Time/s Monthly
Just register for a free plan.
Click to expand...
Click to collapse
You are trying to download an exclusive content
You are trying to download an exclusive file.
Exclusive categories and files only downloadable by paid membership subscriptions.
jorimafia said:
You are trying to download an exclusive content
You are trying to download an exclusive file.
Exclusive categories and files only downloadable by paid membership subscriptions.
Click to expand...
Click to collapse
Well........damn......
I need recovery backup., Europe, India - it doesn't matter...
jorimafia said:
I need recovery backup., Europe, India - it doesn't matter...
Click to expand...
Click to collapse
Here is a mine stock recovery.
mr_techno said:
Here is a mine stock recovery.
Click to expand...
Click to collapse
PS: I need rom backup from TWRP!
Can someone make one for me pls...
mr_techno said:
Found some stock roms for this device HERE
Click to expand...
Click to collapse
The mediafire links in this thread's first post is actually from easy-firmware. I have paid subscription.
---------- Post added at 05:29 PM ---------- Previous post was at 05:20 PM ----------
jorimafia said:
System image is too large to flash... My device is Europe variant..
My device is stuck at HTC boot logo... I think that system image is empty or the boot image is different than mine.. PLS help me. I'm not noob in android devices but this phone is hard to fix..
Click to expand...
Click to collapse
You can change the cid and main version by changing misc partition. I hope. then you can flash.
Prepare a misc.img file in computer with CID of zip version ( cidnum: HTC__060 or cidnum: HTC__059 or cidnum: HTC__058)
You can also downgrade the firmware using this method.
bala
---------- Post added at 05:34 PM ---------- Previous post was at 05:29 PM ----------
jorimafia said:
System image is too large to flash... My device is Europe variant..
My device is stuck at HTC boot logo... I think that system image is empty or the boot image is different than mine.. PLS help me. I'm not noob in android devices but this phone is hard to fix..
Click to expand...
Click to collapse
You can change the cid and main version by changing misc partition. I hope. then you can flash.
Prepare a misc.img file in computer with CID of zip version ( cidnum: HTC__060 or cidnum: HTC__059 or cidnum: HTC__058)
You can also downgrade the firmware using this method.
bala
I need custom rom (CyanogenMod 14, Nougat 7.0 ROM) for my htc desire 630 dual sim.
How do i find AOSP rom android 7 for HTC Desire 630 ???
How can i port desire 650 on desire 630???
hmtariqul said:
I need custom rom (CyanogenMod 14, Nougat 7.0 ROM) for my htc desire 630 dual sim.
Click to expand...
Click to collapse
I am also waiting for nougat but no developer found for our device :crying:
vaibhav1 said:
I am also waiting for nougat but no developer found for our device :crying:
Click to expand...
Click to collapse
Please there , can some one give me any htc desire 630 rom ?? custom or not please. i have forgotten my privacy password
:crying::crying:
Easy try full factory reset...use boot lodee
Solved
DEVICE INFO: LG-V521 - LG G Tab X 8.0 T-Mobile
I can get my tablet into fastboot, that is it.
What happened?
* I could not get custom roms to boot(like not even the boot screen for them, it would just reboot into TWRP over and over no matter what rom I tried to install.
* I then reflashed my recovery via TWRP to a different version of TWRP(now TWRP wont load at all either).
Now my tablet only shows LG logo screen, and fastboot..... I don't know what to do.
Any and all help is appreciated.
PS C:\Users\admin\Downloads> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (14106 KB)...
OKAY [ 0.458s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.464s
PlasmaStrike is my roommate and he must have been logged on already when I originally posted. Okay sorry this is a bit confusing to me, I managed to get the tablet into Download Mode after holding volume up and fanatically pressing and depressing power button at the same time (This tablet is horrible about acknowledging the commands to put it in its menu's). It finally went into download mode(Thank the gods it wasn't soft bricked). I was successful in getting the stock ROM installed and re-applied TWRP successfully. So basically the reason I couldn't get fastboot to apply TWRP to recovery is that, LG the device manufacture doesn't actually have fastboot... so you have to do exploits in the stock ROM to get the boot-loader and all of the nity gritty stuff online through that instead, really stupid if you ask me but ehh i'm not LG.
So for sanity sake should anyone ever need the files, drivers and instructions to fix this type of problem in the future:
The following contain a mirror of: stock ROM, Flashing Software, Instructions, Drivers, & one Custom Rom I have used.
One is Mega and the other DIAU.NET is my own server, if you have a really fast connection just use mine so you get it faster.
Mega: LINK
DIAU.NET(Fastest): LINK
I have been trying to revive my device for many days. Tried every post out there and still im stuck. Qfil and miflash successfully flash the rom but it wont boot. Stuck in zuk logo. Somehow installed twrp and found this error. I cant mount system partition or repair it. I saw one user post this same issue and solved this by reformatting and creating system partition. But i dont know how. Can someone please help me with this issue. I have accecc to bootloader and twrp recovery. System detects as 9008. Any help is appreciated. Thank you all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A3003 using Tapatalk
up
Try this command in ADB
" fastboot format userdata"
I got same errors, fixed by formatting using fastboot erase userdata and the qfil.
I got in this situation because of messing up with encryption and ended with corrupted system partition.
narshi shukla said:
I got same errors, fixed by formatting using fastboot erase userdata and the qfil.
I got in this situation because of messing up with encryption and ended with corrupted system partition.
Click to expand...
Click to collapse
plugged in to the pc with fastboot mode. opened cmd inside adb folder and tried executing the command. stuck at "<waiting for device>.
narshi shukla said:
I got same errors, fixed by formatting using fastboot erase userdata and the qfil.
I got in this situation because of messing up with encryption and ended with corrupted system partition.
Click to expand...
Click to collapse
After formatting, userdata is now showing 32gb of storage. Before it was 9gb. But i still cant flash the rom. Getting error 7. Failed to mount '/system' (invalid argument). Should i fastboot format system too?
Sent from my ONEPLUS A3003 using Tapatalk
Could this be something related to my recovery. Using twrp 3.2.1-0. And i can change the filesystem. But the result is same. This is a big mess[emoji58]
Sent from my ONEPLUS A3003 using Tapatalk
narshi shukla said:
I got same errors, fixed by formatting using fastboot erase userdata and the qfil.
I got in this situation because of messing up with encryption and ended with corrupted system partition.
Click to expand...
Click to collapse
I saw a post with another user having similar issue and what he did to resolve it. But i'm not sure how to do it. I will post the link to the thread.
https://forum.xda-developers.com/lenovo-zuk-z2/help/phone-bricked-partition-t3599107
The solution is on post #6. Copying it here.
SOLVED
Hi all,
it was a pain in the ass but i finally got it back to work..
What happened:
Flashing a corrupt image messed up the phone completely. After playing around a bit the phone doesn't enter EDL mode with Pwr-Vol- anymore.
The phone always started into TWRP, luckily fastboot was still available in bootmanager.
Another strange thing was that TWRP forgot all settings after reboot.
Nice guys in this forum gave the tip to modify a USB-C cable as it was explained on zukfans.eu, that brought it back to EDL - yeah.
But this also didnt solve my problem since that flashing process exited with an error - damn.
My solution after hours of trying flashing various Stock releases....
1. I had to reformat /dev/block/mmcblk0p16 with ext2 ( seems to be destroyed for some reason) mke2fs /dev/block/mmcblk0p16
2. Create /system folder (mkdir /system) in TWRP -> advanced -> Terminal)
3. Flash boot.img from stock image ( Enter fastboot, connect to PC, open cmd prompt and enter adb directory) fastboot.exe -i 0x2b4c flash boot boot.img
4. Flash lastest (seems to be important in my case) TWRP with fastboot.exe -i 0x2b4c flash recovery twrp.img (or whatevery the filename is)
5. Reboot into TWRP and transfer flashable image to the phone and flash it as usual.
Rony John said:
I saw a post with another user having similar issue and what he did to resolve it. But i'm not sure how to do it. I will post the link to the thread.
https://forum.xda-developers.com/lenovo-zuk-z2/help/phone-bricked-partition-t3599107
The solution is on post #6. Copying it here.
SOLVED
Hi all,
it was a pain in the ass but i finally got it back to work..
What happened:
Flashing a corrupt image messed up the phone completely. After playing around a bit the phone doesn't enter EDL mode with Pwr-Vol- anymore.
The phone always started into TWRP, luckily fastboot was still available in bootmanager.
Another strange thing was that TWRP forgot all settings after reboot.
Nice guys in this forum gave the tip to modify a USB-C cable as it was explained on zukfans.eu, that brought it back to EDL - yeah.
But this also didnt solve my problem since that flashing process exited with an error - damn.
My solution after hours of trying flashing various Stock releases....
1. I had to reformat /dev/block/mmcblk0p16 with ext2 ( seems to be destroyed for some reason) mke2fs /dev/block/mmcblk0p16
2. Create /system folder (mkdir /system) in TWRP -> advanced -> Terminal)
3. Flash boot.img from stock image ( Enter fastboot, connect to PC, open cmd prompt and enter adb directory) fastboot.exe -i 0x2b4c flash boot boot.img
4. Flash lastest (seems to be important in my case) TWRP with fastboot.exe -i 0x2b4c flash recovery twrp.img (or whatevery the filename is)
5. Reboot into TWRP and transfer flashable image to the phone and flash it as usual.
Click to expand...
Click to collapse
I also saw this post and tried, but somehow i got errors in twrp terminal. You can try and post result here.
---------- Post added at 04:06 AM ---------- Previous post was at 04:01 AM ----------
Rony John said:
After formatting, userdata is now showing 32gb of storage. Before it was 9gb. But i still cant flash the rom. Getting error 7. Failed to mount '/system' (invalid argument). Should i fastboot format system too?
Click to expand...
Click to collapse
After formating userdata, there will be nothing in the data partition, i think you should also format system, and try twrp by hendibul which is for removing encryption but may help, or try twrp version 3.0.3.0 if both methods failed, try with different earlier versions, and remember to format userdata and system everytime with fastboot and flash recovery by fastboot.
I think you should also try mi flash which may work after formating userdata and system.
narshi shukla said:
I also saw this post and tried, but somehow i got errors in twrp terminal. You can try and post result here.
---------- Post added at 04:06 AM ---------- Previous post was at 04:01 AM ----------
After formating userdata, there will be nothing in the data partition, i think you should also format system, and try twrp by hendibul which is for removing encryption but may help, or try twrp version 3.0.3.0 if both methods failed, try with different earlier versions, and remember to format userdata and system everytime with fastboot and flash recovery by fastboot.
I think you should also try mi flash which may work after formating userdata and system.
Click to expand...
Click to collapse
where can i find the link to hendibul. Google search shows zero results . can you give me a link?
Qfil and miflash always gives me successful flash. I just cant boot the system after that. Will get stuck at zuk logo. I guess it because something is wrong with the partition table. TWRP cant mount system because of that.
Rony John said:
where can i find the link to hendibul. Google search shows zero results . can you give me a link?
Qfil and miflash always gives me successful flash. I just cant boot the system after that. Will get stuck at zuk logo. I guess it because something is wrong with the partition table. TWRP cant mount system because of that.
Click to expand...
Click to collapse
Hendibul twrp is included in zui roms, go to zui Oreo twrp flashable threads and find in post, some user extracted and shared it. If my memory is good then there is one thread in which hendibul have shared modded twrp.
There is also a chinese twrp which u can find on zukfans.eu
I dont know if any of these will work or not, but as you have already tried and nothing is working, then you can try these if it works if will be wonderful
---------- Post added at 04:41 AM ---------- Previous post was at 04:38 AM ----------
Rony John said:
where can i find the link to hendibul. Google search shows zero results . can you give me a link?
Qfil and miflash always gives me successful flash. I just cant boot the system after that. Will get stuck at zuk logo. I guess it because something is wrong with the partition table. TWRP cant mount system because of that.
Click to expand...
Click to collapse
Have you tried qfil and mi flash after formating system and userdata by fastboot?
You should try every available zui. One of them should work.
In mi flash there is a option of clean everything and re lock try that.
And before flashing, boot device in edl mode.
Adb reboot edl
narshi shukla said:
Hendibul twrp is included in zui roms, go to zui Oreo twrp flashable threads and find in post, some user extracted and shared it. If my memory is good then there is one thread in which hendibul have shared modded twrp.
There is also a chinese twrp which u can find on zukfans.eu
I dont know if any of these will work or not, but as you have already tried and nothing is working, then you can try these if it works if will be wonderful
---------- Post added at 04:41 AM ---------- Previous post was at 04:38 AM ----------
Have you tried qfil and mi flash after formating system and userdata by fastboot?
You should try every available zui. One of them should work.
In mi flash there is a option of clean everything and re lock try that.
And before flashing, boot device in edl mode.
Adb reboot edl
Click to expand...
Click to collapse
Thanks for the suggestion. I will give it a try and update the results
Rony John said:
Thanks for the suggestion. I will give it a try and update the results
Click to expand...
Click to collapse
Welcome mate
Hope it works.
---------- Post added at 05:06 AM ---------- Previous post was at 05:04 AM ----------
Rony John said:
Thanks for the suggestion. I will give it a try and update the results
Click to expand...
Click to collapse
Before flashing it with pc, make sure it is shown as qhusb dload 9008 after boosting edl.
After completing flashing, wait a minute disconnect device and press power button, it will vibrate for a long time 2 3 minutes then it will boot.
narshi shukla said:
Welcome mate
Hope it works.
---------- Post added at 05:06 AM ---------- Previous post was at 05:04 AM ----------
Before flashing it with pc, make sure it is shown as qhusb dload 9008 after boosting edl.
After completing flashing, wait a minute disconnect device and press power button, it will vibrate for a long time 2 3 minutes then it will boot.
Click to expand...
Click to collapse
Device recognised as 9008 in port.
Tried flashing with miflash with rom version 1.9.xx. Flash was success but upon booting device turns off after zuk logo. White led light stayed ON after turn screen OFF.
Tried with qfil ver 2.7. Flash success but upon pressing power putton, device just short vibrate with an led blink. wont turn on and no display.
Should i smash this device
Rony John said:
Device recognised as 9008 in port.
Tried flashing with miflash with rom version 1.9.xx. Flash was success but upon booting device turns off after zuk logo. White led light stayed ON after turn screen OFF.
Tried with qfil ver 2.7. Flash success but upon pressing power putton, device just short vibrate with an led blink. wont turn on and no display.
Should i smash this device
Click to expand...
Click to collapse
Well, I and most others can't help beyond that, you need to dig deeper in internet, may be someone else also got same issue and resolved it.
One last suggestion, try with deep flash cable or try with removing battery and then flashing, i have seen some people successfully flashed by this way.
narshi shukla said:
Welcome mate
Hope it works.
---------- Post added at 05:06 AM ---------- Previous post was at 05:04 AM ----------
Before flashing it with pc, make sure it is shown as qhusb dload 9008 after boosting edl.
After completing flashing, wait a minute disconnect device and press power button, it will vibrate for a long time 2 3 minutes then it will boot.
Click to expand...
Click to collapse
Tried again with miflash and rom version 2.xx. success but stuck at zuk logo. Fastboot says locked now. For rom version 1.9.xx it stayed unlocked even when i chose erase and lock in miflash. Attaching fastboot page pic.
narshi shukla said:
Well, I and most others can't help beyond that, you need to dig deeper in internet, may be someone else also got same issue and resolved it.
One last suggestion, try with deep flash cable or try with removing battery and then flashing, i have seen some people successfully flashed by this way.
Click to expand...
Click to collapse
I found an alternative for deepflash cable. Shorting pin 2 with a copper wire can change 900E to 9008.qfil always kick me to 900E and now im an expert in getting back to 9008.:laugh: Deepflash cable is just for accessing 9008 port. Right?
Rony John said:
Tried again with miflash and rom version 2.xx. success but stuck at zuk logo. Fastboot says locked now. For rom version 1.9.xx it stayed unlocked even when i chose erase and lock in miflash. Attaching fastboot page pic.
Click to expand...
Click to collapse
Either flash with higher version of zui, with qflash or try to unlock and flash twrp, i think its giving some good signals.
If its locked and unlocked it means bootloader and recovery partition are working, and recovery can fix system, thats what the work of recovery partition.
One thing is striking in my brain is if its locked, then there should be stock recovery, if its not there flash using fastboot, and try to install update.zip from stock recovery.
---------- Post added at 06:12 AM ---------- Previous post was at 06:11 AM ----------
Rony John said:
I found an alternative for deepflash cable. Shorting pin 2 with a copper wire can change 900E to 9008.qfil always kick me to 900E and now im an expert in getting back to 9008.:laugh: Deepflash cable is just for accessing 9008 port. Right?
Click to expand...
Click to collapse
Yeah its just for getting device in 9008 mode, but sometimes changing usb cables works,
---------- Post added at 06:14 AM ---------- Previous post was at 06:12 AM ----------
Rony John said:
Tried again with miflash and rom version 2.xx. success but stuck at zuk logo. Fastboot says locked now. For rom version 1.9.xx it stayed unlocked even when i chose erase and lock in miflash. Attaching fastboot page pic.
Click to expand...
Click to collapse
What i can see is device is completely stock now, so try to flash official zui with higher version with updater. Zip file place in root of internal storage, for this you can use Adb push commands.
narshi shukla said:
Either flash with higher version of zui, with qflash or try to unlock and flash twrp, i think its giving some good signals.
If its locked and unlocked it means bootloader and recovery partition are working, and recovery can fix system, thats what the work of recovery partition.
One thing is striking in my brain is if its locked, then there should be stock recovery, if its not there flash using fastboot, and try to install update.zip from stock recovery.
---------- Post added at 06:12 AM ---------- Previous post was at 06:11 AM ----------
Yeah its just for getting device in 9008 mode, but sometimes changing usb cables works,
---------- Post added at 06:14 AM ---------- Previous post was at 06:12 AM ----------
What i can see is device is completely stock now, so try to flash official zui with higher version with updater. Zip file place in root of internal storage, for this you can use Adb push commands.
Click to expand...
Click to collapse
Why is everything so hard with this device. I cant find a stock recovery file from xda and zukfans.eu. quick question can i extract the recovery.img from a qpst rom and fastboot flash it?
Rony John said:
Why is everything so hard with this device. I cant find a stock recovery file from xda and zukfans.eu. quick question can i extract the recovery.img from a qpst rom and fastboot flash it?
Click to expand...
Click to collapse
Yes you can,
Also if you have twrp backup, you can use that as well.
BTW if you still don't have stock recovery, try flashing once more may be this time it also flashes stock recovery.
Hi!
I can't seem to be able to flash 3.6.2_11-1-hanoip TWRP on Moto G60S.
— the Official App crashes each time when i press "FLASH TWRP"
— when I'm trying to flash with ADB by fastboot flash recovery_a twrp.img I'm getting (bootloader) Invalid partition name recovery_a error (same goes for recovery_b and recovery)
— when I'm trying to do fastboot boot twrp.img, I'm getting (bootloader) Command is not support error.
What am I doing wrong? Or maybe hanoip won't work for 60S at all?
Hi , hanoip is the dev code for G60 , and you have the 60s. G60s dev code name is lisbon.
Yeah, I know, I decided to try my luck as I don't think I'll ever get a dedicated TWRP. Oh, well, nevermind.
aandred said:
Yeah, I know, I decided to try my luck as I don't think I'll ever get a dedicated TWRP. Oh, well, nevermind.
Click to expand...
Click to collapse
I'll help u find one give me about ten minutes
aandred said:
Yeah, I know, I decided to try my luck as I don't think I'll ever get a dedicated TWRP. Oh, well, nevermind.
Click to expand...
Click to collapse
What is the build number, specifics? Go to about device in settings and screenshot the page
Hi! Thanks! The build number's RRL31.Q2X-70-39
Hi - I have the same question / issue - any luck?
My build nr. is RRL31.Q2X-70-44-3