Related
Okay here's is my story
I have an O2 UK Dell streak which I had originally rooted using the superboot method (fastboot mode and then run the two commands on the mac terminal window)
I then recently installed the leaked 2.1 update on the handset and everything was fine till tonight. I installed an app which needed root access and having not seen the root access icon in the apps, thought that I need to root the phone again after the 2.1 update.
So I plugged in my phone again in my mac and ran the terminal commands. the first one went ok "chmod +x install-superboot-mac.sh" or I assume its ok as the prompt went down without any errors in terminal window.
The second command "./install-superboot-mac.sh" ran but with errors:
"ERROR: could not get pipe properties
sending 'boot' (2520 KB)... OKAY
writing 'boot'... OKAY
ERROR: could not get pipe properties
rebooting... "
The phone rebooted but is now stuck at DELL logo, I have tried removing and reinserting the battery, also ran the commands again in the fastboot mode but still the same errors and still stuck. when going into fastboot mode, the phone pops some error message but not enough time to note the error, also when trying to normal switch on, the display shows a quarter of white screen for a split second with i suspect the same error as before fastboot mode but is even quicker to even notice
PLEASE PLEASE SOMEONE HELP!
From what is sounds, this should help fix your problem. Sood luck!!
http://forum.xda-developers.com/showthread.php?t=754563
I wanted to install DJ sd's 2.1.1 update, so I entered fastboot and installed clockwork recovery and amss.mbn of 2.1 and rebooted. Now nothing is coming on my screen and I cant boot or enter fastboot or recovery. Please help. Heres my screenshot
C:\STREAK>fastboot.exe -i 0x413c flash recovery recovery.img
sending 'recovery' (6144 KB)... OKAY
writing 'recovery'... OKAY
C:\STREAK>fastboot -i 0x413c flash amss amss.mbn
sending 'amss' (6974 KB)... OKAY
writing 'amss'... OKAY
C:\STREAK>fastboot -i 0x413c reboot
rebooting...
please please please help me.... my dell streak is gone.
Hi there, could your battery be empty? plug it in the wall and try charging it back up. if battery is OK then try take the battery out and leave it for 10mins and put it back in then boot up the streak again but ensure the back cover is on properly.
no battery is not empty, 3 home,menu,n cancel lights are on, but no display, and computer is showing qualcomm cdma technologies msm device connected, but no drivers
please help
can I use adb? how to configure n all, its not detecting my dell streak
bhaveshdj said:
no battery is not empty, 3 home,menu,n cancel lights are on, but no display, and computer is showing qualcomm cdma technologies msm device connected, but no drivers
please help
can I use adb? how to configure n all, its not detecting my dell streak
Click to expand...
Click to collapse
I am having the same problem sadly, let me know if you get it working. I will do the same.
You don't say what version you are upgrading from...
Can you still get into clockwork or fastboot?
bhaveshdj said:
I wanted to install DJ sd's 2.1.1 update, so I entered fastboot and installed clockwork recovery and amss.mbn of 2.1 and rebooted. Now nothing is coming on my screen and I cant boot or enter fastboot or recovery. Please help. Heres my screenshot
C:\STREAK>fastboot.exe -i 0x413c flash recovery recovery.img
sending 'recovery' (6144 KB)... OKAY
writing 'recovery'... OKAY
C:\STREAK>fastboot -i 0x413c flash amss amss.mbn
sending 'amss' (6974 KB)... OKAY
writing 'amss'... OKAY
C:\STREAK>fastboot -i 0x413c reboot
rebooting...
please please please help me.... my dell streak is gone.
Click to expand...
Click to collapse
no he cant, thats the problem.
Help
I was upgrading from an factory unlocked 1.6 asia. Nothing is coming on my screen at all, no fastboot, recovery or adb. In xp its showing as qualcomm technologies cdma msm. Please help.
if what you posted is all you did, you didn't read the instructions properly.. you can only got to 1.2.1 from 1.6 after going O2 2.1 -> DJ_S 1.1.1 -> DJ_S 1.2.1 + amss 2.2
XsCode said:
if what you posted is all you did, you didn't read the instructions properly.. you can only got to 1.2.1 from 1.6 after going O2 2.1 -> DJ_S 1.1.1 -> DJ_S 1.2.1 + amss 2.2
Click to expand...
Click to collapse
that doesnt help
XsCode said:
if what you posted is all you did, you didn't read the instructions properly.. you can only got to 1.2.1 from 1.6 after going O2 2.1 -> DJ_S 1.1.1 -> DJ_S 1.2.1 + amss 2.2
Click to expand...
Click to collapse
You hit the nail on the head as to why a lot of people have problems
OK... so you guys messed up by not reading instructions properly. If this gets fixed I'm sure it wont happen again. LoL
Now to help you guys out... I'm no expert at this but at least let troubleshoot..
-Were you guys rooted with Clockwork recovery (custom recovery) before you flashed the baseband? Or Stock recovery, unrooted.
-Clarify exactly what happens when you try to get in to either Fastbootmode (camera and power button down). How about when you try to get in to Recovery mode (Volume button(s) and power button).
-Try updating the drivers on your PC to use the Qualcomm drivers that were provided when Stephen came up with Froyo Beta 1 (the very first one)
Neither does that, but at least I gave a probable reason for the problem for future reference..
ryrules1 said:
that doesnt help
Click to expand...
Click to collapse
True, I was having a number of problems before updating to v. 1.2 it took me a while to even get v1.1.1 up and running, then I tired to update to v.1.2. Then the Dell boot screen lag, never saw that logo again after trying to downgrading to o2 v2.1.
Where can I get the driver, can someone upload it?
forum.xda-developers.com/showthread.php?t=776883
Get the pdf for links and good instructions on how to install them.
ryrules1 said:
Where can I get the driver, can someone upload it?
Click to expand...
Click to collapse
i can fix this in theory if you drop into the #dellstreak irc channel on freenode - looks like your streak is dropping to diag mode as its detected a system issue
XsCode said:
forum.xda-developers.com/showthread.php?t=776883
Get the pdf for links and good instructions on how to install them.
Click to expand...
Click to collapse
Ahh, Yea I have tired those driver, while they install fine, they still dont help to boot into fastboot or recovery. I still cant connect my streak via adb or fastboot.
FIXED thanks to DJ Steve. So happy. Running v.1.2 w/ new baseband!!! awesomea and FAST.
good to hear...
i have the same problem can somebody help me please? no fastboot no recovery
Hi there
Recently, my Streak was bricked. I did wipe via fastboot and get my device bricked.
Fortunately, varriaty period has not expired, so I got new one.
Seems like there are some "leaks" and factrory errors with Dell Streak devices with hw drivers
Hello, so i got a asus nexus 7 wifi model, never seen it working. Recovery says booting failed. The one thing that works is fastboot. So i decided to reflash everything. But when i run fastboot oem unlock after about 6mins i get FAILED (remote: () as i understand no error.
I tried 3 drivers, official, naked and from asus nexus toolkit everytime same result. I tried few different pc's diferent usb ports. So maybe someone had a same problem and knows what to try next.
Bootloader version 4.13
full log:
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 391.390s
Thx in advance
xz33r0x said:
Hello, so i got a asus nexus 7 wifi model, never seen it working.
Click to expand...
Click to collapse
I hope you didn't pay much for it. At this time there is no known workaround, as APX mode on the N7 has not been cracked with an nvflash-like tool.
You might consider donating it to the folks at androidroot.mobi, or... becoming the person that breaks into APX on the N7.
bftb0 said:
I hope you didn't pay much for it. At this time there is no known workaround, as APX mode on the N7 has not been cracked with an nvflash-like tool.
You might consider donating it to the folks at androidroot.mobi, or... becoming the person that breaks into APX on the N7.
Click to expand...
Click to collapse
I didn't pay for it at all yeah have read about apx. Just was wandering is there any other options, or the nand is dead like a brick
Hi Guys,
I was hoping to upgrade to Paranoid Android today but didn't get so far.
I went into Clockwork Recovery and did a Factory Reset. I then proceeded to wipe the Dalvik Cache and other Cache. Then after that I set it to format the SD Card.
I noticed that while in recovery I couldn't get my SD card to mount in Windows 7. I booted up the Nexus 7 toolkit and chose a sideloading option for the Paranoid Android zips while the Nexus 7 was in CM Mod. I was staring at a frozen screen so I held the power button and down volume for ten seconds.
After a while it got to the point where the Nexus 7 would not boot. It would not show me the Google logo and when plugged in the Battery Recharging graphic did not come on.
After a while I somehow got it to boot up again. I went back into Recovery Mode and tried the sideloading again. I was still looking at a frozen screen so I did the ten second power button reset.
Now it's bricked. There's no Google logo, no option to go into Bootloader or Recovery. There is no graphic indicating that the Nexus 7 is recharging.
It's been hours. I even went so far to open up the back cover, unplug the battery, and then plug it back in. There's nothing.
When I plug it into my laptop Windows detects it as "ADX" but doesn't have a driver to load for it.
I thought out of everything I did that unplugging and replugging the battery would have reset the system and allowed me back into Recovery Mode.
Not so....
So, I have to ask: Did I kill my Nexus 7?
Is there any way to bring this thing back? I figure I will leave it charging in a 2A Charger overnight. I need some feedback though because I did some research and have seen that a lot of people are had this problem.
ev1lchris said:
When I plug it into my laptop Windows detects it as "ADX" but doesn't have a driver to load for it.
Click to expand...
Click to collapse
Did you mean ADB drivers? I can't find anything on ADX. I would try uninstalling and reinstalling the drivers and toolkit as a quick step, I'd also consider other toolkits as a possible solution.
I think he meant APX. APX=done. Only solution: take out phone and call ASUS for an RMA number.
I refuse to believe my Nexus 7 is done.
ev1lchris said:
I refuse to believe my Nexus 7 is done.
Click to expand...
Click to collapse
If you haven't already, do a search on APX mode/drivers. You should find that the only way to recover once in APX is if you have made a copy of a file prior to bricking. That file contains a device-specific number that is required to perform the recovery. Additionally, even with that number the process is quite daunting. Good luck should you soldier on.
PS- You should also know that while in APX mode your device is "on" & the battery is discharging to a non-rechargeable state.
Yup, had the same thing happened to my N7 today after it crashed and could not recover to save it. Plugged it on my laptop and it recognized it as an apx device something. I already called asus for rma and I'll be shipping out mine on monday.
There is hope.
Sent from my ZTE V970 using xda app-developers app
First thing I'm going to do once I get my N7 back, make an nvflash blob http://forum.xda-developers.com/showthread.php?t=2455927
I don't think I ever got the chance to flash anything new onto my Nexus 7. I just did a factory reset and formatted the SD card.
It's ON IT BOOTED UP!!!!
SO HAPPY. LOL!!!!!
IT'S ALLLLIIIIIIIIIIIIIVVVVVEEEE!!!!
ev1lchris said:
It's ON IT BOOTED UP!!!!
SO HAPPY. LOL!!!!!
IT'S ALLLLIIIIIIIIIIIIIVVVVVEEEE!!!!
Click to expand...
Click to collapse
You returned from APX? This is a first; what did you do? Are you sure you were in APX?
Lucky! curious also on how you manage to get out of apx mode!
thraizer said:
Lucky! curious also on how you manage to get out of apx mode!
Click to expand...
Click to collapse
Just walk around constantly holding the power button. Go about your day, and it should come on all of a sudden.
I'm rocking Kit Kat 4.4 right now!
OffcerClancy said:
You returned from APX? This is a first; what did you do? Are you sure you were in APX?
Click to expand...
Click to collapse
thraizer said:
Lucky! curious also on how you manage to get out of apx mode!
Click to expand...
Click to collapse
ev1lchris said:
Just walk around constantly holding the power button. Go about your day, and it should come on all of a sudden.
I'm rocking Kit Kat 4.4 right now!
Click to expand...
Click to collapse
I think there's a bit of misunderstanding here about APX mode...
To put it simply... APX doesn't necessarily signify hardbrick.
APX is required for nvFlash operations, such as nvFlashing a new bootloader, should the original become erased/corrupted. Indeed, if that where to happen, the Nexus 7 would automatically default to APX mode... and await for somebody to perform such an nvFlash operation.
Currently the only way of performing nvFlash operations on the Nexus 7 is if the user had run the flatline procedure BEFORE damage had occurred to the bootloader. This procedure generates what are called 'wheelie blobs' on a per-device basis, and are unique to each Nexus 7... ie., they are not transferable. They are required to resurrect a dead Nexus 7 with a corrupted, damaged or erased bootloader.
However, you can electively get into APX mode, even with a functional bootloader. Indeed, the latter part of the flatline procedure requires it. How to do this is detailed here.
So, just because your Nexus 7 is in APX mode doesn't necessarily mean it's hardbricked or the bootloader is damaged/corrupted or erased... though, more often than not, that is exactly what it does mean.
Providing you haven't knowingly done anything that might affect the bootloader, pressing and holding the POWER BUTTON for a good 30 seconds or more, might just be sufficient to kick-start a seemingly dead Nexus 7 out of APX mode. I can't guarantee it will work of course... but it's got to be worth a shot.
And it seems to have worked for @ev1lchris.
Rgrds,
Ged.
Sound like by dumb luck he stumbled in and fell assbackwards out of APX mode.
I brick my N7 when flashing 4.3 vía fastboot, ASUS replace the motherboard and its all good now
Enviado desde mi HTC One mediante Tapatalk
After months of use it is non responsive and in APX mode again. However, I have to highly suspect that the battery is playing a role here.
I have a rubber band constantly pressing the power button.
Let you guys know what happens.
I had almost the same problem that is described below. I did not leave the link to the blog since I assume its not allowed.
How to brick your Nexus 7
I have been playing around with Ubuntu on my Nexus 7 for a while, and decided yesterday to go back to stock android 4.2.2, so I downloaded the images from developers.google.com/android/nexus/images and extracted the zip file to my PC.
Restoring android 4.2.2
included in the package is a flash-all.bat file which contains all the commands which need to run so i thought great – i’ll just run it, go make a cup of tea and job done.
*** DO NOT RUN THE BATCH FILE! ***
The batch file doesn’t actually check the status of the commands it sends! Here’s what happened to me:
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 1.042s]
finished. total time: 1.043s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.861s]
finished. total time: 1.862s
erasing 'recovery'...
OKAY [ 0.975s]
finished. total time: 0.978s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.611s]
finished. total time: 1.613s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 12.114s]
finished. total time: 12.116s
sending 'bootloader' (2096 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.849s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.007s
< waiting for device >
^CTerminate batch job (Y/N)? y
It’s sent the reboot command even though the bootloader failed to flash! So now i have an expensive paperweight
BATCH FILE DEVELOPERS, please make sure that your code has at least a ‘pause’ statement before doing things like rebooting so users can check the output before proceeding!!!
Tags: google, nexus7
When I plug to the PC my Nexus 7 it wants to instal APX Drivers. I already read that this is as good as rubbish now but I just wanna make sure there is nothing I can still do.
Im preaty sure Im ****ed up though. Should I try contact Asus?
ChiquiNL said:
I had almost the same problem that is described below. I did not leave the link to the blog since I assume its not allowed.
How to brick your Nexus 7
I have been playing around with Ubuntu on my Nexus 7 for a while, and decided yesterday to go back to stock android 4.2.2, so I downloaded the images from developers.google.com/android/nexus/images and extracted the zip file to my PC.
Restoring android 4.2.2
included in the package is a flash-all.bat file which contains all the commands which need to run so i thought great – i’ll just run it, go make a cup of tea and job done.
*** DO NOT RUN THE BATCH FILE! ***
The batch file doesn’t actually check the status of the commands it sends! Here’s what happened to me:
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 1.042s]
finished. total time: 1.043s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.861s]
finished. total time: 1.862s
erasing 'recovery'...
OKAY [ 0.975s]
finished. total time: 0.978s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.611s]
finished. total time: 1.613s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 12.114s]
finished. total time: 12.116s
sending 'bootloader' (2096 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.849s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.007s
< waiting for device >
^CTerminate batch job (Y/N)? y
It’s sent the reboot command even though the bootloader failed to flash! So now i have an expensive paperweight
BATCH FILE DEVELOPERS, please make sure that your code has at least a ‘pause’ statement before doing things like rebooting so users can check the output before proceeding!!!
Tags: google, nexus7
When I plug to the PC my Nexus 7 it wants to instal APX Drivers. I already read that this is as good as rubbish now but I just wanna make sure there is nothing I can still do.
Im preaty sure Im ****ed up though. Should I try contact Asus?
Click to expand...
Click to collapse
If you're still under warranty and you have tried all you can to revive the thing then yes you should call Asus and do a RMA.
Here's an update on my situation...
I installed a battery I bought off of eBay and.... nothing. Still dead.
I'm charging it and I'm going to continue to have the rubber band wrapped around the power button but I think it's pretty much dead.
Such an awesome tablet that I used and depended on every day.
I bought a refurb N7 2013 but I really would have liked to save my N7 and continued using it.
Yesterday I tried rooting my Moto G7 (build PPOS29.114-134-7). I managed to unlock the bootloader and install Magisk, however, I installed a wrong version for my build and got stuck in a bootloop. After being frustrated for a while by my foolishness, I managed to fix it and was able to boot it up again to OS. But instead of giving up, I decided to try once again, this time with the correct build.
I once again installed Magisk, createad the boot.img, moved it to my PC and turned the phone off, but now I cannot turn it back on. The screen is black, no matter for how long I hold the buttons, no matter the combination of them I hold, it simply doesn't respond anymore. I let it charging on a wall outlet, I let it charging on the PC, no response. It doesn't even show the battery connected or anything. The screen remais black and nothing happens.
The only sign of life it shows is when I connect it to the PC and hold the buttons - Windows plays the "hardware connected" sound, but it doesn't appear on my drive list or anything.
Is it an expensive paperweight now? Should I take it to the shop, or is there anything else I can do to try and fix this?
Thank you, and feel free to call me stupid. I feel like I deserve it.
EDIT: This issue has been resolved thanks to user EmixArian24 who messaged me with a link he found on the Telegram group regarding the G7. I attached a blankflash he sent me and by using it, I managed to boot to bootloader. I then downloaded the stock rom from Lolinet and flashed it to the phone. It then booted as normal.
Thank you very much to EmixArian24 for the magical link and everybody else who replied. I really appreciate it.
As for the G8 I bought, I chose to keep it. I will be selling my G7 as soon as possible.
AetherOmega said:
Yesterday I tried rooting my Moto G7 (build PPOS29.114-134-7). I managed to unlock the bootloader and install Magisk, however, I installed a wrong version for my build and got stuck in a bootloop. After being frustrated for a while by my foolishness, I managed to fix it and was able to boot it up again to OS. But instead of giving up, I decided to try once again, this time with the correct build.
I once again installed Magisk, createad the boot.img, moved it to my PC and turned the phone off, but now I cannot turn it back on. The screen is black, no matter for how long I hold the buttons, no matter the combination of them I hold, it simply doesn't respond anymore. I let it charging on a wall outlet, I let it charging on the PC, no response. It doesn't even show the battery connected or anything. The screen remais black and nothing happens.
The only sign of life it shows is when I connect it to the PC and hold the buttons - Windows plays the "hardware connected" sound, but it doesn't appear on my drive list or anything.
Is it an expensive paperweight now? Should I take it to the shop, or is there anything else I can do to try and fix this?
Thank you, and feel free to call me stupid. I feel like I deserve it.
Click to expand...
Click to collapse
Open device manager
How is it listed?
Likely need to use blankflash
Should be a link in my help thread
https://forum.xda-developers.com/showpost.php?p=78869857&postcount=2
Sent from my ali using XDA Labs
sd_shadow said:
Open device manager
How is it listed?
Likely need to use blankflash
Should be a link in my help thread
https://forum.xda-developers.com/showpost.php?p=78869857&postcount=2
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
It is listed as Qualcomm HS-USB QDLoader 9008. I'm trying to use the blankflash I found under one of the threads you linked in your master thread, but I'm stuck at "Waiting for firehose to get ready" now. I'm out of ideas...
EDIT: either the firehose warning or the "greeting device for command mode" followed by "FAILED (blank-flash:greet-device:error reading packet)"
EDIT2: yet another error I found:
Code:
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
OKAY [ 0.002s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x832808F5
...chip-id = 0xBA
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.006s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.005s]
validating files
OKAY [ 0.045s]
switching to download mode
OKAY [ 0.002s]
greeting device for image downloading
OKAY [ 0.001s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
AetherOmega said:
It is listed as Qualcomm HS-USB QDLoader 9008. I'm trying to use the blankflash I found under one of the threads you linked in your master thread, but I'm stuck at "Waiting for firehose to get ready" now. I'm out of ideas...
EDIT: either the firehose warning or the "greeting device for command mode" followed by "FAILED (blank-flash:greet-device:error reading packet)"
EDIT2: yet another error I found:
Click to expand...
Click to collapse
You could try running it in several windows at same time.
Sent from my jerry_cheets using XDA Labs
sd_shadow said:
You could try running it in several windows at same time.
Sent from my jerry_cheets using XDA Labs
Click to expand...
Click to collapse
I did. I opened 15 to 25 of the batch files at once, only one of them seemed to "carry on" with the process only to result in a "Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)" error. I'm really out of ideas now.
Is there a possibility of a home-fix, or the chances of it are really low? I'm thinking it might an incorrect version of files or something, I'm having a hard time finding specifics for my model. I tried searching specifically for "XT1962-4 blankflash" and the sorts, but it really is not easy finding anything related to this specific model.
EDIT: Since I had so many files and batches to use, I decided to scrap everything and start over again. Much better. I went to Lolinet, downloaded the blankflash for my model by going to Firmware > Moto > River > Blankflash and fired up blankflash.bat.
But I have a question regarding that - the files inside this folder I downloaded are the only ones I need, or do I need to download the stock rom and put all the files of the ROM inside the blankflash folder as well before opening blankflash.bat? What I've been trying to do is just starting blankflash with the contents of the zip I downloaded from Lolinet, I haven't tried pasting any other files inside of it.
Also, with this blankflash, I managed to get this result:
Code:
D:\Downloads\blankflash_from_PPO29.114-4>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 186 (0xba)
[ 0.004] ...cpu.sn = 2200439029 (0x832808f5)
[ 0.004] Opening singleimage
[ 0.004] Loading package
[ 0.006] ...filename = singleimage.pkg.xml
[ 0.007] Loading programmer
[ 0.007] ...filename = programmer.mbn
[ 0.007] Sending programmer
[ 0.291] Handling things over to programmer
[ 0.293] Identifying CPU version
[ 0.299] Waiting for firehose to get ready
[ 60.863] Waiting for firehose to get ready
[120.958] ...MSM8953 unknown
[120.959] Determining target secure state
[120.964] Waiting for firehose to get ready
[181.059] ...secure = no
[181.080] Initializing storage
[181.082] Waiting for firehose to get ready
[241.158] Configuring device...
[241.159] Waiting for firehose to get ready
[301.235] Waiting for firehose to get ready
[361.308] Waiting for firehose to get ready
[421.378] Waiting for firehose to get ready
[481.448] Initializing storage
[481.450] Waiting for firehose to get ready
[541.524] Configuring device...
[541.525] Waiting for firehose to get ready
[601.603] Waiting for firehose to get ready
[661.687] Waiting for firehose to get ready
[721.773] Waiting for firehose to get ready
[781.852] Waiting for firehose to get ready
[841.943] Configuring device...
[841.944] Waiting for firehose to get ready
[902.031] Waiting for firehose to get ready
[962.124] Waiting for firehose to get ready
[1022.213] Waiting for firehose to get ready
[1082.309] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[1082.309] Check qboot_log.txt for more details
[1082.310] Total time: 1082.311s
[1082.310] There were some hiccups in backup and restore.
[1082.310] Please save the following files and see a Bootloader member.
[1082.310] 1) ./qboot_log.txt
[1082.310] 2) ./backup_0x832808F5_2020-03-23_215316.img
[1082.310]
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
D:\Downloads\blankflash_from_PPO29.114-4>pause
Pressione qualquer tecla para continuar. . .
Any ideas?
Just an update, I gave up and bought a new phone. I'll try sending the phone to a shop whenever this whole viral crisis ceases.
AetherOmega said:
Yesterday I tried rooting my Moto G7 (build PPOS29.114-134-7). I managed to unlock the bootloader and install Magisk, however, I installed a wrong version for my build and got stuck in a bootloop. After being frustrated for a while by my foolishness, I managed to fix it and was able to boot it up again to OS. But instead of giving up, I decided to try once again, this time with the correct build.
I once again installed Magisk, createad the boot.img, moved it to my PC and turned the phone off, but now I cannot turn it back on. The screen is black, no matter for how long I hold the buttons, no matter the combination of them I hold, it simply doesn't respond anymore. I let it charging on a wall outlet, I let it charging on the PC, no response. It doesn't even show the battery connected or anything. The screen remais black and nothing happens.
The only sign of life it shows is when I connect it to the PC and hold the buttons - Windows plays the "hardware connected" sound, but it doesn't appear on my drive list or anything.
Is it an expensive paperweight now? Should I take it to the shop, or is there anything else I can do to try and fix this?
Thank you, and feel free to call me stupid. I feel like I deserve it.
EDIT: This issue has been resolved thanks to user EmixArian24 who messaged me with a link he found on the Telegram group regarding the G7. I attached a blankflash he sent me and by using it, I managed to boot to bootloader. I then downloaded the stock rom from Lolinet and flashed it to the phone. It then booted as normal.
Thank you very much to EmixArian24 for the magical link and everybody else who replied. I really appreciate it.
As for the G8 I bought, I chose to keep it. I will be selling my G7 as soon as possible.
Click to expand...
Click to collapse
I have some zip folders I want to post concerning hardbrick moto g7. How do I do this? I get error. Image files only are accepted.
Please tell me how to post a jar file here? I have tried to attach one but my file manager only allows jpg and PNG files types.