Help restoring or recreating /system mount point - General Questions and Answers

Any help would be much appreciated... Haven't toyed around with phones for some time but I must have gotten into the deep end with this Sony Xperia 5 II, not sure what to do here.
Using OrangeFox recovery, I must have unmounted or done something to the phone's /system mount point because I can't flash any ROMs or restore anything without /system available. While a "System" option does appear in the "Mount" menu's checklist, tapping on it does nothing and I can only mount "Data" and "oem".
Here's what's happening when I try to remount the system via adb:
mount -o remount,rw /system which returns:
mount: /system: mount point does not exist.
Out of curiosity I tried this as well if it's even related:
adb disable-verity but get:
Overlayfs setup failed with error No such device or address
verity not enabled - ENG build
Is there a way to mount /system as a partition given the above doesn't work?

Are you sure partition /system physically exists?
If it doesn't exist then re-flash Stock ROM.

Is there a way to check? And if it should exist, can it be created?
Currently the only partitions on the phone are metadata, Data and a pair of storage/sdcard1.
Prior to this issue (or before I mucked around in the recovery), I was able to successfully flash a ROM's system.img but cannot do the same now due to "no such file or directory".
As a result I'm suspecting it might have been there before, but could be wrong.

Ok I'll try getting the stock ROM tomorrow, at the moment the Sony Mobile Flasher tool by Androxyde is stuck on Sending getvar: product so the phone might even have trouble flashing via flash mode.
Are there any other known tools/programs for Sony devices to flash stock firmware with? Or a direct link to a flashable rom could work wonders.

Ok there was no luck using either the Xperia Flash Tool or Newflasher as they both yielded errors or just hang at an early stage in the ROM flashing, made sure it wasn't a driver or USB issue which begets the question...
Does the bootloader need to be re-locked? Currently at work but if there are some ideas worth throwing around I'm all ears.

Resolved, might as well say exactly what worked for me in case it happens to anyone else:
1. Perform a format through the recovery.
2. Download the right firmware through XperiFirm 5.6.1.
3. Move/Copy the downloaded firmware files into Newflasher 4.2. No making subfolders or anything, just move all these files into the same path the newflasher application is in.
4. Not sure if it was a necessary step but I used Unsin 1.13 to extract the boot_X-FLASH-ALL-2389.sin file created from step 2 which created an image (drag and drop this boot_x-etc-etc SIN file into the Unsin executable to extract it).
5. Place the boot_x-etc.img file created via Unsin into the Newflasher folder, just along with all the other files in the directory.
6. Ensure the Xperia 5 II is powered off. Hold the volume down key while plugging it into a USB 2.0 port until the phone's LED goes green.
7. Launch newflasher, and press f. For all other prompts, press n. You should see the stock firmware getting flashed in newflasher.
Will take a few minutes, but is an important step as it rebuilds the system, even going as far as restoring the bootloader to the stock one which you'll see can get booted into rather than a custom recovery as done in step 9 later.
8. Once step 7 is done, unplug the phone to turn it off (or press the power button until the LED goes away).
9. Hold both the power button and volume down keys, and let go of just the power button to enter the bootloader.
10. This is where the option to /mount system can be selected and was successfully mounted (a custom recovery like the one I had could not do this).
11. Now that /system is actually mounted, you can proceed to open fastboot from within the bootloader and go flashing whatever. For example, what I did immediately after mounting /system was open fastboot, plug my phone into the computer and ran all the commands in step 4 for this particular ROM: https://forum.xda-developers.com/t/...icial-lineageos-18-1-for-xperia-5-ii.4221435/
Pretty explicit, but it explains that all along it was just a matter of reflashing the stock firmware via newflasher which let me enter the default bootloader and mount /system without further problems.
Hope this helps anyone else in the future.

Related

I think I bricked my phone!!

I was attempting to get the Nandroid back up feature going on my phone. I downloaded the recent RC30 for the multi-touch (I couldn't help it), and I was given this error about the application settings not responding and to force quit. Then I downloaded the SPL bootloader and the modified RC30 with the busybox. It's in this post (http://forum.xda-developers.com/showthread.php?t=459830). I did a successful backup, but now my phone won't work right.
When I boot the phone none of the buttons respond until a good 30 seconds into the full boot up, and only after I slide open the keyboard. When I press the power key the screen flashes and the blank wallpaper comes up for 5 seconds. There is no way for me to get into the recovery mode. When I tried that it gives me the phone with the exclamation point.
I think I am just at or 1 day past my 14 days. It's really going to suck if I have to pay for a new phone b/c I got cocky and thought I knew what I was doing. Hopefully you guys have a solution or T-mobile will be forgiving.
Oh, and when I look under settings it says: kila user 1.0 TC4-rc30 so T-mobile will know I rooted the phone and F'ed up.
You could try restoring with DREAIMG.nbh
and you didnt brick it, a brick doesnt do anything, yours sounds like it boots.
I can't get into recovery mode. I can get into fastboot. I found a thread on installing cupcake will help get it back to RC30, but I didn't understand where to type in the prompts.
When I tried that it gives me the phone with the exclamation point.
Click to expand...
Click to collapse
Try Alt-L at this point.
I forgot about that. Thank you! Now I just need to find a way to get my phone back to full functionality. Do I need to just find RC29 or JF RC30 and reinstall as update.zip?
It says "E: Can't open /cache/recovery/command"
We will see if reinstalling RC30 will work. Does anyone have the orignal RC30 that comes installed on the G1? I understand I'll lose root access and that might be the smartest thing for me now.
I reinstalled RC30 and it worked! Thank you guys, and thanks for putting up for my temporary insanity!
I would do a wipe and then update to jf's latest 1.4. But at this point you should be able to update to whatever you want.
Sorry if this is a stupid question but I have made a NANDROID Backup and I would like to know how to restore my phone with the backup I made.
ow to Restore your phone on a Windows PC using a Nandroid backup
I am going to assume you already have a Nandroid backup created on your SD card using JF 1.31's recovery Alt-B feature. The backup will create a folder called nandroid on your SD.
What you need:
The Android SDK:
Fastboot Windows Binary in this post:http://forum.xda-developers.com/show...53&postcount=1
From your Nandroid backup you need three files:
data.img
system.img
boot.img
Steps to restore your phone
1) Put the files Adb and AdbWinApi.dll from the tools folder in the Android SDK into C:\WINDOWS\System32 folder on your PC. Substitute the correct drive letter if windows is not installed on you C: drive
2) Put the Windows Fastboot.exe into the C:\WINDOWS\System32 folder on your PC
3) Create a folder on the C: drive of your PC called android. The path should be C:\Android.
4) Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder called Android you created by mounting your SD card as removable disk.
5) Unplug the USB cord and power off your phone
6) Power up your phone by holding CAMERA+POWER, you should see three androids on skateboards. If you don't see this go install the Engineering boot loader
7) Plug the USB cord back into your phone and press back. The screen on your phone should say fastboot.
8) Make sure your pc is using the correct driver. Open the device manager on your pc. It is helpfull to have all other USB storage devices besides your phone unplugged for this part. Look for a USB Mass Storage device in the list of the USB devices. Right click on it and update the driver. Pick the option to browse for a driver on your pc. The driver is located in the Android SDK your downloaded in the folder called usb_driver. If this is done right you will now see a device called HTC Dream
9) Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
10) Type cd C:\android
then enter the following commands:
fastboot flash system system.img
it will say Sending, then writing and say OKAY if it was successful
then type
fastboot flash userdata data.img
wait for the second OKAY and type
fastboot flash boot boot.img
wait for the second OKAY and type
fastboot reboot
Your phone should now be restored exactly as you had it when it was backed up.

[Q] How bad did I brick my Kyros 7005??

Okay, where to start.. I think I have bricked my phone pretty good.
Here is the approximate list of things that happened.
I wanted to try to update to froyo, so I downloaded z4root, worked beautifully
Followed all the directions to install clockwork mod (including reading far enough ahead to find out the one in the directions was for the 7015, but gave the link for the 7005 version later) - Worked like a charm
BACKED UP SYSTEM as instructed
Then here is where things went south. I attempted to install the Cyanogen Mod froyo based. I followed the directions, including backing up softmac and wpa_supplicant files. And it would not start up. I could get it into recovery mode but not to start fully. I tried doing the restore, it couldn't mount the SD Card where the backup was. Being knowledgeable enough to dangerous in Linux, I used ADB Shell and tried various things to try to find out where the SD Card or recovery image failed. I had also been trying to locate FWDN as I saw people had done fixes with that, but I couldn't get it to load in FWDN "Mode". I figured if I could replace the recovery program on there that doesn't work with the one that does, it should in theory allow me to reboot into the correct recovery mode and let me pull the files from my SD Card. After about 15 minutes of shuffling around, I ended up mounting the \system folder where I found a file called recovery. Looked to be the right size. So I made a modified batch file that would instruct it to load from that folder.
After that mistake, all of the sudden, the vtc driver that I had installed did see the unit. I was like Joy! Joy! I fired up fwdn but since I didn't have the original files that it "liked" I used an lk.rom, but I think it wasn't from an X5A but from a lonpad. Now I don't even get COBY on the screen.
But wait, I'm even more dangerous. I got the hardware ID that it's currently using on the USB bus, edited first the vtc ini file to see if I can reload a different rom. It detects it, but FWDN gives me "bad boot" error or something like that. But I'm a trooper, if I'm gonna kill it, I'm gonna kill it good. I change the SDK/ADB driver to recognize the device. And it seems to recognize it. Then I went to try "fastboot flash recovery recovery.x5ag.img " which I had NEVER been able get the unit into fastboot mode, and it goes through and does it. Then I do a fastboot reboot to see if I can get it to come up in recovery mode, but I can't.
Then the final bright idea comes up on me.. Hey, I have the backup from SD card, what if I zip it up, call it update.zip, and do a fastboot update?
Now ADB can make some kind of connection to it, but when I try to shell I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
ADB State always reports device or unknown never bootloader
ADB remount comes back with remount failed: Invalid argument
ADB push into the / or /system folders (in an attempt to push a copy of sh there) fails saying read only file system
ADB push to /sys comes back with failed to copy: No such file or directory
So, that's where I am.. I think I really really REALLY bricked this thing... although the fact that I can still ADB to it leaves some shimmer of hope.
Thanks,
Joe
can u get into the boot loader at all? If so you are not Bricked you will just need to reinstall the entire system using fast boot. You may be able to restore the default OS using an update.zip file. It may be named something different for your device. All you do with that is place it on the root of the SD card and when the bootloader boots it finds the file and flashes the phone.
I can't get fastboot to recognize the device, it goes right to the ADB bridge. Where I can run some limited ADB commands that are recognized.. If I could get it to start up in fastboot mode, that would likely solve the issue, provided I can get the correct working update.zip file, rather than me trying to fudge one from the clockworkmod backup.
do you have any hardware buttons on device? turning on with volume up or down (or back) gives you differing USB ID's to device manager - obviously you want fastboot mode. (use device manager on ADB Bridge (Details) to get your ID - i think its DEED for fastboot and D00D for fwdn)
otherwise... you can force boot a new bootrom. It's what I did on my telechips device. Find tcboot.rom - put it in the same directory as fwdn
1. Open your device
2. Unsolder your battery + terminal
3. While turning on the device, place a short - screwdriver/pin etc - across pins 7/8 of the NAND chip (for 5 seconds)
4. FWDN should bring up a message about flashing bootrom
5. Reboot (and resolder battery cable)
Note: this obviously is pretty hardcore - but i went from brick, to black screen brick, to full restore via this method.

[Q] CDMA Galaxy Tab (SCH-I800)

Hi.
i Upgrade my SCH-I800 to CM9. and it works good. and from last week not working. and its stuck it CM logo. so i tired to re installing it.
some how i was tried to boot my Tab back.
so tried below steps
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step 1. Download the zip and unzip the contents to your Desktop (or where ever you would like). These are stock restore files (DJ11) for Download Mode (Volume down and power) Also download the wpa_supplicant and update.zip. Download all these files to the same directory so they are easy to find. I just use the Desktop.
Step 2. Download Heimdall from Here:
glassechidna.com.au/products/heimdall/
Also just below version 1.1.1 is Microsoft C++ This also needs installed on your machine because it has .dll files Heimdall uses.
Step 3. Power off your Tab. With your USB connected to your PC, hold volume down on your Tab, and plug USB into Tab. This will Launch Download Mode. Unzip heimdall and go into the drivers folder where you will see zadig.exe. Run this. At the top you see options. Click “list all devices”, then in the dropdown select Android USB composite device (or whatever it says). Click start and let heimdall download the drivers. Once its finished, close zadig and launch heimdall front end. (leaving Tab plugged in and in download mode obviously)
THIS IS THE IMPORTANT PART!!!!!! DO NOT SCREW THIS UP!!
Unzip the stock files if you haven’t already.
Now its common sense.
The zImage goes in both the Kernel AND Recovery slot. (they even tell you where things go with little descriptions)
The system.rfs goes in Factoryfs
The Param.lfs goes in Param.lfs
The cache goes in the cache slot.
DO NOT EVER EVER EVER PUT ANYTHING IN ANY OTHER LOCATION. THESE ARE THE ONLY FILES YOU NEED. **Note, if heimdall fails at the very beginning, just try unplugging and turning off the tab, close, and relaunch heimdall-frontend.exe. It will eventually start. Sometimes you just need the right combo of plugging in launching the program…
After you have the files in place click “Start” to flash. ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems. What this did was return you to STOCK EVERYTHING DJ11. This is necessary to flash the update.zip we downloaded earlier.
After this runs you will more then likely boot loop. Power down, wait a few seconds and hold power and up volume to boot into recovery. (NOTE, do NOT hold power too long, just long enough to turn it on, then continue holding up volume until you see recovery. WIPE DATA AND CACHE. Tab should boot.
Step 4. You should now be back to 100% stock DJ11, and guess what, you’re still rooted! The next step is to push the wpa_supplicant (For some reason this file makes the update.zip fail) to /system/bin using ADB. If you want, you can get root explorer on your Tab and put the wpa_supplicant on your SDcard. Then, use root explorer to copy this file to /system/bin (its ok to overwrite the one that is already in there). If you don’t want to bother with Root Explorer, do the following. Place wpa_supplicant into your tools folder with ADB.
Tab plugged into PC, with USB Debugging ON from your ADB folder (mine is C:tools) Type:
C:tools: adb push wpa_supplicant /sdcard
C:tools: adb shell
$ su (may need to check the Tab to “allow” permission)
# mount -t rfs -o remount,rw /dev/block/stl9 /system
#cd /system/bin
#cat /sdcard/wpa_supplicant > wpa_supplicant
#exit
$exit
Step 5. Place the update.zip file you downloaded on the root of your sdcard and unplug from PC. Power off your Tab. Boot into recovery. Hold volume up, press and hold power for about 3 seconds then release WHILE still holding up volume until you see stock Android recovery. Apply update.zip from sdcard.
This should start the update process, if it doesn’t reboot on its own, select reboot device from recovery. Once you’ve booted, you will be updated to the newest update from Samsung. Notice Superuser is still in your app drawer. (if it is not don’t panic)
*NOTE If you boot and it requests you to activate and won’t activate, do this to bypass activation. On the screen it asks you to activate use the volume toggle. Press volume up once, volume down twice, volume up three times, and volume down four times. It will then allow you to skip activation.
Step 6. Next we are going to download the Stock rooted images of EC02, and the VOODOO zImage.
We are now going to flash the rooted EC02 files via Heimdall. This will be the same process as Step 3, except we will use the new EC02 files.
Power off your Tab. With your USB connected to your PC, hold volume down on your Tab, and plug USB into Tab. This will Launch Download Mode. Unzip heimdall and go into the drivers folder where you will see zadig.exe. Run this. At the top you see options. Click “list all devices”, then in the dropdown select Android USB composite device (or whatever it says). Click start and let heimdall download the drivers. Once its finished, close zadig and launch heimdall front end. (leaving Tab plugged in and in download mode obviously)
THIS IS THE IMPORTANT PART!!!!!! DO NOT SCREW THIS UP!!
Unzip the EC02 files if you haven’t already.
Now its common sense.
The zImage (from the zip file, NOT the voodoo zImage you just downloaded) goes in both the Kernel AND Recovery slot. (they even tell you where things go with little descriptions)
The factoryfs.rfs goes in Factoryfs
The Param.lfs goes in Param.lfs
The cache goes in the cache slot.
DO NOT EVER EVER EVER PUT ANYTHING IN ANY OTHER LOCATION. THESE ARE THE ONLY FILES YOU NEED. **Note, if heimdall fails at the very beginning, just try unplugging and turning off the tab, close, and relaunch heimdall-frontend.exe. It will eventually start. Sometimes you just need the right combo of plugging in launching the program…
After you have the files in place click “Start” to flash. ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems. What this did was fix root for EC02.
After this runs you will more then likely boot loop. Power down, wait a few seconds and hold power and up volume to boot into recovery. (NOTE, do NOT hold power too long, just long enough to turn it on, then continue holding up volume until you see recovery. WIPE DATA AND CACHE. Tab should boot.
*NOTE If you boot and it requests you to activate and won’t activate, do this to bypass activation. On the screen it asks you to activate use the volume toggle. Press volume up once, volume down twice, volume up three times, and volume down four times. It will then allow you to skip activation.
Step 7. This is the final step. Instead of flashing recovery VIA Rom Manager (since the recovery in Rom Manager is not updated to the latest kernel source), we will be flashing @khasmek (aka Boushh from XDA) EC02 VOODOO kernel which will also give us a fully working ClockWorkMod recovery!
Again, we will be using heimdall to flash the zImage we downloaded in step 6 (NOT the stock zImage that was in the zip) Please make sure this file is zImage only on your PC. Flashing anything with an extension (zImage.txt, zImage.zImage, etc) will not take.
Power off Tab and disconnect from PC. Hold volume down and plug into PC to get into download mode. Launch Heimdall-Frontend.exe (drivers should still be installed, if not re-installing the same way from the previous steps will work, but you should not need to do this again). Put your modified zImage in the kernel slot AND recovery and hit start. This will flash a custom kernel AND @khasmek VOODOO recovery! First boot may take a while due to External 4 partition conversion. This is normal. If you bootloop for ANY reason, wipe data and cache. By the way, this kernel is also overclocked to 1.4Ghz. Must use SetCPU otherwise stock speeds of 1Ghz will be default.
*Note: Remember, do not use ROM Manager to flash a recovery or you will have to follow steps 5 on again to restore your Tab (You will have to boot into recovery manually until someone fixes stock ClockworkMod Recovery, I can’t stress enough not to use Rom Manager until you hear otherwise). By the way, these instructions ALSO double as a RESTORATION guide!!! If you get stuck anywhere, past step 5, simply start over at step 5 to recover your Tab. If you get stuck BEFORE step 5, start over at step 1!! Great right?!
-------------------------------------------------------------------------------------------------------------------------------------------------------------
then i sucked step 4.
actually he asked to PUSH wpa_supplicant to /system/bin
first i need to know how it do without booting device. is there way to access Tab internal memory in Download mood or any other way.
Thanks

Easy Revert From GPE

For people who converted over to GPE and are having a hard time installing most roms, I have a fairly easy fix for you. The problem is with the partition table. I specifically did this with 1032 falcon assuming you already have recovery installed.
1. You need mfastbootv2.zip from here: http://www.mediafire.com/download/14p0x9cb34s2kqj/mfastboot-v2.zip
2. You will also need gptfix.zip from here: http://forum.xda-developers.com/moto-g/general/fix-android-lollipop-ota-gpe-stuck-t2970842
3. Extract mfastbootv2.zip to a folder.
4. Extract gptfix.zip to the mfastbootv2 folder you just created.
5. Put your phone in bootloader mode by holding the power and down buttons for 5 seconds until you see the menu then hook your phone to your computer via usb.
6. Now open the folder you extracted gptfix.zip and mfastbootv2 to, hold shift on the keyboard, right click on a blank area in the folder and choose open command window here.
7. Now type "mfastboot flash partition gpt.bin" without quotes. Shouldn't take long. A second or two.
8. Once completed reboot to recovery and format data and system (may get some errors) then reboot recovery so twrp can create a folder to put your rom in.
9. With my phone hooked to the computer via usb, i mounted usb in twrp then copied my rom to the twrp folder using windows explorer and flashed a rom that would never flash before!
Hope this helps. I know this info was already talked about but i found it was split up and unclear.

[Request] EMMC backup of G6-U10 (tutorials included)

Hi, my G6-U10 is hard bricked and has gone to QDLoader 9008 mode so i cant go to recovery, fastboot,adb mode .
i need EMMC image of a similare device (G6-U10) so i can fix it following instructions in this thread .
i dont need whole EMMC image, just first 100-200 MB .
to extract EMMC, you need to be on stock rom with root access.
to do so:
1. Enable "USB debugging" in "Developer Options". then connect your device to Windows PC.
2. download and extract ADB. then run the following command through CMD:
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/EMMC.img bs=100m count=1
note that you must enter each row separately and confirm the dialogs appeared on your device screen to grant root and adb access for pc. the option bs=100m mean that the dd command will only extract first 100MB of EMMC. and FYI, this file is only backup from system partition, not from any private files, no need to worry.
the extracted file will be in internal SD, named EMMC.img , compress it in ZIP or RAR so it will have much less size, then send it here to solve many people's problems. anybody does that, i'll appreciate.
Thanks for reading.
Credits and references:
@majdinj http://forum.xda-developers.com/showthread.php?t=2450045
@Jimmyz0r http://forum.xda-developers.com/yureka/help/guide-unbrick-hard-bricked-yureka-t3303112
@tirta.agung http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
http://linoxide.com/linux-command/linux-dd-command-create-1gb-file/
http://unix.stackexchange.com/questions/134299/dd-bs-count-seek
https://yadi.sk/d/wtaBNFaUraZyg
washichi said:
https://yadi.sk/d/wtaBNFaUraZyg
Click to expand...
Click to collapse
Thanks bro, but it's just 100bytes, not 100Mbytes. i think you used bs=100 instead of bs=100m
please consider reuploading , you are my saviour
info on the progress:
I got EMMC image thanks to @washichi :good: (download it from attachments).
then i could finally wake my device up, in the fastboot and recovery, following instructions in this thread(first post).
i can go into Fastboot mode but though i had unlocked bootloader (before), but i can only flash recovery, system(partly) and boot partitions. other partitions give me error ((Remote: Not Allowed)).
the only recovery that i could go into, was the latest TWRP 3 . in recovery i can even connect my device in MTP mode to pc and see files on the internal SD! but i was not successful with flashing roms, it always gives me error mounting cache, system, data. ADB mode is also accessible, used adb sideload to flash rom, but it didnt worked too!
i think part of internal SD is damaged and need to be fixed somehow. still havent found out how.
so, for guys who are having problems similar to me or "Internal Storage Damaged blah blah" i recommend trying to follow these steps to see if their internal SD is still flashable or not:
1. Download an official Rom for your device and unpack it using HuaweiUpdateExtractor.
2. download and extract latest (at least 1.0.32) fastboot in the same folder as extracted huawei IMG files are (Gush bless me! there's too much grammatical erros in my texts )
3. connect your device in fastboot mode (instructions above).
4. go to the directory where all extracted files place. Hold shift and right click on empty space, chose "Open command window here".
Note: you must have an unlocked bootloader to be able to continue, type this command to see if its unlocked:
Code:
fastboot oem get-bootinfo
if you're unlocked, then continue reading, if not, i dont think there is a way to find unlock key for your device.even DC unlocker cant recognize your device in fastboot and adb.
5. now that you know you have an unlocked BL, type these commands one bye one:
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash aboot aboot.img
fastboot flash tz tz.img
fastboot flash userdata userdata.img
fastboot flash [COLOR="RoyalBlue"]XXX [/COLOR][COLOR="SeaGreen"]XXX[/COLOR].img
as i said before, i could only flash 3 partitions with success. but if you where able to flash all parts with success, your extremely have a chance to revive your device. at last, type fastboot reboot to see if you boot up successfully, if not, you will go again in fastboot mode or recovery mode.
for me, default recovery mode just freezes, so i flashed TWRP 3 instead of default recovery. you can try that too.
one more thing: you might not be successful to reboot into recovery, you must restart until you succeed. if you stuck in freezed recovery, open the device back, unscrew the little steel plate (it has 2 screws) and dettach the battery cord, wait 3 secs, re-attach it. i have done it more than 300 times now i dont even know where is the steel plate
FYI, EMMC image in the attachment is for G6-U10 only and probably will not work for other G6 models. if you want G6-L11 emmc, i can share it for you.
if anything was not clear for you, ask me.
@bugggmenot Everytime i insert the sd card and try to enter fastboot mode by holding the Volume+, the PC keeps beeping and refreshing the device manager, tho i can't see any hardware detected. The phone isn't recognizable as fastboot device and the LED is lighting in a blue color.
Any ideas?
Sashko98 said:
@bugggmenot Everytime i insert the sd card and try to enter fastboot mode by holding the Volume+, the PC keeps beeping and refreshing the device manager, tho i can't see any hardware detected. The phone isn't recognizable as fastboot device and the LED is lighting in a blue color.
Any ideas?
Click to expand...
Click to collapse
Do as follows:
1. detach the battery and retach it again.
2. connect the device to pc WITHOUT holding any buttons.
3. if you go into fastboot mode, you will see a blue "Fastboot mode" in middle of texts (and Blue LED).
4. type in cmd: fastboot devices
if your device is listed, you are good to go for flashing procedure.
oh and one more important thing: install fastboot and adb drivers. it's a global driver not device specific, so install any you van find ( sorry I can't Google it for you right now).
bugggmenot said:
Do as follows:
1. detach the battery and retach it again.
2. connect the device to pc WITHOUT holding any buttons.
3. if you go into fastboot mode, you will see a blue "Fastboot mode" in middle of texts (and Blue LED).
4. type in cmd: fastboot devices
if your device is listed, you are good to go for flashing procedure.
oh and one more important thing: install fastboot and adb drivers. it's a global driver not device specific, so install any you van find ( sorry I can't Google it for you right now).
Click to expand...
Click to collapse
Did everything still doesn't want to boot in fastboot mode.
Edit: I made it to the fastboot, thank you very much.
Sashko98 said:
Did everything still doesn't want to boot in fastboot mode.
Edit: I made it to the fastboot, thank you very much.
Click to expand...
Click to collapse
Happy to hear that. would be great if you share your way of success and your current progress on reviving the device. it might help many people.
bugggmenot said:
Happy to hear that. would be great if you share your way of success and your current progress on reviving the device. it might help many people.
Click to expand...
Click to collapse
I got it to the progress you did. Was able to flash only boot.img recovery.img and like 950MB of system.img. Yet smth makes me to think that everything i do flash is being flashed in the SDcard memory not in the internal one, is it supposed to be like that?
Edit1: Tried to flash an update.zip which i made by using huawei tools extractor from the stock recovery but the verification aborted the update. Tried with CWM by using adb sideload but there was some error while sending, also tried with TWRP which seems to erase its memory everytime when i restart the phone, the adb sideload doesnt work and couldn't found the flashable zip after i pushed it in by using adb
Sashko98 said:
I got it to the progress you did. Was able to flash only boot.img recovery.img and like 950MB of system.img. Yet smth makes me to think that everything i do flash is being flashed in the SDcard memory not in the internal one, is it supposed to be like that?
Click to expand...
Click to collapse
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
bugggmenot said:
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
Click to expand...
Click to collapse
Well i did try flashing img files via TWRP but it allows me to modify just recovery or boot partition. Tried also making flashable zip of the partition to run it from CWM but i get stuck.
I also tried
Code:
fastboot flashing unlock_critical
and
Code:
flashing unlock
but i recieve 3 dots, maybe i should be more patient next time to see what will happen.
===========================================================================
@bugggmenot i've found the file for G6-C00 for qualcomm bootloader platform. Will they work on G6-U10???
Sashko98 said:
Well i did try flashing img files via TWRP but it allows me to modify just recovery or boot partition. Tried also making flashable zip of the partition to run it from CWM but i get stuck.
I also tried
Code:
fastboot flashing unlock_critical
and
Code:
flashing unlock
but i recieve 3 dots, maybe i should be more patient next time to see what will happen.
===========================================================================
@bugggmenot i've found the file for G6-C00 for qualcomm bootloader platform. Will they work on G6-U10???
Click to expand...
Click to collapse
Greate! i dont know if they are similar or not but who cares, i'll give it a shot! please share files here i'll try and report back.
bugggmenot said:
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
Click to expand...
Click to collapse
Why not try to repartition your device?
You can you the parted binary (google will find it) and put it on your /sdcard or / (the root folder). NOT your internald memory or any other partition thats your EMMC.
Now umount ALL partitions in recovery, except for the external sdcard. Go to the commandline in the recovery and cd to the parted binary. Now typ 'parted /dev/block/mmcblk0'.
Type 'print' to see your partition table.
You can now modify your partition table (only ext2 and fat32 partitions support, BUT you can format it whit your recovery soo it will be ext4. (Dont check RM format in settings!).
Hope this will fix the flashing problem.
Hard Brick
Hello guys, i don't know if this is the right place, but do you know how to unbrick Huawei Y550 - L03 from hard brick? My pc recognizes it in the device manager just as Android adapter PCUI (COM10) but the device itself doesn't show.
Thank you in advance if you can help me please. :crying:
Here i put EMMC for G6-L11 for people who need it:
Hello, can you explain how you made it from dead phone QDLoader 9008 to recovery?
bugggmenot said:
Here i put EMMC for G6-L11 for people who need it:
Click to expand...
Click to collapse
We should use the Yureka tutorial with this file to bring the G6-L11 to life right?
henrucci said:
We should use the Yureka tutorial with this file to bring the G6-L11 to life right?
Click to expand...
Click to collapse
only if your phone is G6-L11, then the answer is yes.
Win32disk killed for good all sdcards with g6-l11 image

Categories

Resources