Hey guys!
The story goes like this: today I decided to flash my SM-G935F(Nougat) to an S8+ ROM with TWRP, however I ran into a brick wall that is the "Unable to mount /Data" I found a youtube video on the subject which had positive comments, so I decided to follow the tutorial. That was 5 hours ago and since then, the phone is sitting on one of my PC fan since it's getting toasty and I plugged it into the wall just in case. The TWRP console reads the following:
Formatting Data using mkexfatfs...
Done.
The upper part is saying "Formatting..." and it seems like the phone is working, since the progress bar below the console is flashing. But its doing this for almost 5 hours now and I started to wonder if this is normal or not.
Thanks for the help in advance!
Szekith said:
Hey guys!
The story goes like this: today I decided to flash my SM-G935F(Nougat) to an S8+ ROM with TWRP, however I ran into a brick wall that is the "Unable to mount /Data" I found a youtube video on the subject which had positive comments, so I decided to follow the tutorial. That was 5 hours ago and since then, the phone is sitting on one of my PC fan since it's getting toasty and I plugged it into the wall just in case. The TWRP console reads the following:
Formatting Data using mkexfatfs...
Done.
The upper part is saying "Formatting..." and it seems like the phone is working, since the progress bar below the console is flashing. But its doing this for almost 5 hours now and I started to wonder if this is normal or not.
Thanks for the help in advance!
Click to expand...
Click to collapse
No. Should be just a few moments
I need your help has the same message, but says E: recv error on uevent
Related
[EDIT 3] Worked fine, finally, thanks for all the help.
[EDIT 2] Yeah, I don't know how it happened or what happened, but I got a lot further. I started to get Odin failing at recovery and then remembered this thread which I found earlier: http://forum.xda-developers.com/showthread.php?t=907261&page=2
Basically did it exactly like how the OP fixed it, and the phone is currently being flashed.
But now I have a different problem, seems I can't get a break.
http://img651.imageshack.us/i/stuck.jpg/
It's stuck there, should I just wait? Is it supposed to take a while? Or is there a problem? Been there for about an hour now.
[EDIT] So the phone works now, but Odin won't flash for me. What could the problem be if it's stuck on Initializing (or rather, Initialzing as the program puts it)? I've tried 1.61, 1.7, used the DI18 file and removed the md5 bit so that the file ends in .tar, etc
Hey, so I've been desperately trying to return my Epic to stock DI18, and I tried clockwork mod which didn't work, and then I tried doing it through Odin, and it kept hanging on Initializing.
Anyway, I keep trying with Odin, and ended up taking out my battery and putting it back in, but now the phone won't turn on. It doesn't turn on normally, not through download mode, not recovery, nothing.
Any help? What can I do? I tried searching but every result ends up being about turning on bluetooth or wifi, etc., and the few that are related to bricking talk about going into download mode to flash with Odin.
I hope you didn't take the battery out while flashing odin...
you can't turn it on in any way right?
can you charge it via usb? maybe you just ran out of power while flashing?
Uh, yeah, that's exactly what I did. Every time Odin would hang at Initializing, I'd have to remove the battery and restart the phone to try again.
God, I am so stupid, it is ridiculous.
The battery did have a decent amount of charge last time I checked though.
Hold down 1 and power and insert battery while holding them. That should get you into d/l mode. Taking out the battery while odin is stuck on initializing does not harm the phone.
Sent from my Bonzai'd Epic 4g.
I just did something like what you said leather, and I got it into download mode.
Now I'm afraid to do anything. Any reason why my flashing through Odin wouldn't work?
Odin is picky about the computer its running on. I used a laptop when i first started flashing..no issues ever.
Fixed my desktop and instantly ran into odin problems. Try changing USB ports and make sure youve got no firewalls running.
Sent from my SPH-D700 using XDA App
Yeah, what I don't know how it happened or what happened, but I got a lot further. I started to get Odin failing at recovery and then remembered this thread which I found earlier: http://forum.xda-developers.com/showthread.php?t=907261&page=2
Basically did it exactly like how the OP fixed it, and the phone is currently being flashed.
But now I have a different problem, seems I can't get a break.
http://img651.imageshack.us/i/stuck.jpg/
It's stuck there, should I just wait? Is it supposed to take a while? Or is there a problem? Been there for maybe 5-6 minutes now.
The factory always takes the longest; so give it time. And do NOT pull the battery at that point. Youll have to say good bye epic :<
Sent from my SPH-D700 using XDA App
How did this end up? Did it move past FACTORY FS?
Nope, still stuck in that same exact place. Is it supposed to take this long or has something gone wrong?
Could I unplug it and try again at this point, or would that brick it? It's just stuck there, what do I do? I'd love to try different usb ports and such, but I can't if I don't stop this process, just don't know how to do it without bricking it.
And thanks for the help so far.
Did you remove the. Md5 at the end of the tar file?
Sent from my SPH-D700 using XDA App
No, I put the md5 back to start from the beginning with everything as it comes from downloads and such.
What do I do about it right now though? Can I safely unplug it and restart it or...?
Seems like you have no choice but to unplug it. Removing the md5 shouldn't make a difference. Try a different USB port.
Sent from my SPH-D700 using XDA App
Yeah, thankfully it didn't brick. I feel like I'm walking through a minefield with this thing.
Anyway, switched ports, had the file renamed to end in .tar, made sure Odin was opened as administrator in Windows 7, and thankfully it flashed fine.
Now I'm back at vanilla 2.1, can start fresh in terms of upgrading, was having some problems earlier. Is that GPS locking problem present in 2.3? Assuming I put ClockworkMod 3 on it and have the file system reset to EXT4, can I just flash to 2.3 ROMs right away?
Such problems
Hi everyone,
Skip this first paragraph if you just want to read my steps from problems to solution:
I hope this post helps people who were in the same situation I was in.
A few days ago I just happened to read the news about the new gingerbread for the AT&T i997 Samsung Infuse. I read that it wasn't over the air. Because of what has been seeming as a bluetooth leak after trying everything to stop the leak up to hard resetting it, I figured I'd pray that gingerbread fixes it. So on went my quest in the last few days trying to get this gingerbread update as fast as I could.
1) I downloaded keys mini for the Samsung device which was needed for the upgrade. I installed it on my main pc which is windows 7 64 bit. After installation, it's first run, it automatically updated the application.
2) I plugged in my phone via usb and it said device not registered so I got in contact with a Samsung rep in chat who told me to register it and it would take 24 hours.
3) I registered on Samsung and waited about 48 hours and still no change.
4) Got impatient and read about GTG Ultimate unbrick which is supposed to return my stock phone back to it's out of box condition which eliminated what I thought as an error with my phone of it not being registered.
5) Now after plugging it in after the unbrick. I got a message stating "device already up to date". I kept getting this for the last couple days. Sigh
6) Read that I could download the new gingerbread stock ROM without being rooted. Just had to use the ODIN3 I got with the GTG Ultimate unbrick zip file and supply the ROM I997UCKL2-Homebinary.tar.md5 as the input file.
7) Follow basically same instructions as unbricking but not reformatting and just supplying the md5 file as the input for hte PDA button then clicking start.
8) Odin 3 message status window was stuck at setupconnection and I knew this wasnt right. It was stuck for over 15 minutes and it should only do that for a minute or less.
9) Unplugged usb and big error in red on Odin 3 (but didn't have a choice)
10) Tried removing battery and retrying the flash but now a bigger issue the screen was all colored specs or in other words multi colored spots. Rut roh!
11) After scratching my head and googling like crazy some others had the same issue and they mentioned removing the battery and trying again but didn't mention that the spots would remain on the screen while the items could be flashed fine.
12) Tried again this time it got past setupconnection but was stuck at initializing.
13) Thought to myself let me try it on my Windows Vista 32 laptop.
14) Voila. It worked. So don't give up if you see the colored spots on your screen. There still is a chance. I now have gingerbread. THANKS EVERYONE!
Next Morning Update:
I was too quick to be happy. It seems I am one of the small few who is having touch sensitivity issues and lag typing on the lower right side of the screen especially with the back key (backspace). I typed my first reply to an email and the third word in the backspace was completely disabled.
Glad you got it working.
Am i the only one when i saw "what now" immediately thought about that lead paint commercial ?
iSaint said:
Am i the only one when i saw "what now" immediately thought about that lead paint commercial ?
Click to expand...
Click to collapse
GTG Ultimate unbrick zip is missing can u re-up it plz?
Dear reader,
After rooting my phone for a while and downloading all these apps I came upon ChainFire 3D. I downloaded it without checking and installed it without a big thought about the warnings it showed. Now when my phone reboots, the Samsung Galaxy S4 GT-i9500 logo appears but then the screen turns empty blank. So I went into recovery and wiped data. When I reboot, same thing happens. So I searched and panicked but didn't find good results. I thought if I use Odin it may work, so I flashed the stock recovery and root and then CWM. Tried again...still fails! So I downloaded the adb thing from Android, opened in cmd, everything fine but when i followed these instructions(from http://forum.xda-developers.com/showthread.php?t=2362873) it did not work when I wrote 'su'. So I skipped to the next one, comments saying mount /system which already happened but it did not work. Now I don't know what to do and I feel sad and disappointing.
If anyone has a backup file which I can use to start and then reset or a solution to my problem please help!
Thanks to everyone!
Phone: GT-i9500
Recovery:CWM
Rooted:Yes
P.S I can tell more details about my device but you may need to reply.
Why do you post in noob thread, then about 5 minutes later open up this thread.
If you waited about 7 minutes you would have got an answer.
Obviously you spent as much time reading the rules as you did with chainfire 3d install instructions.
Hi, Today like an idiot I've used this app to push the screen up to 4K, happy with the result I've gone too far and set the 5K preset, rebooted the device and... stuck in a launcher/app/logo loop...
The phone is Rooted and running Android 6.0.1, I Have ADB access thru the TWRP. Issue here is that no matter what all the commands like: WM, AM, PM result in this error:
CANNOT LINK EXECUTABLE: cannot locate symbol "context_lookup" referenced by "/system/lib64/libandroid_runtime.so"...
page record for 0x7fae83c010 was not found (block_size=64)
Of course I could flash new the phone but the ammount of data and how is configurated right now is worth the effort.
Most likely you will need to reflash.. that's why devs says that you have to do a nandroid backup just in case... Maybe try safemode?(Vol Down after the logo appears)
Hi , do you fix it ?
I have the same problem on my s6
CRY123 said:
Hi, Today like an idiot I've used this app to push the screen up to 4K, happy with the result I've gone too far and set the 5K preset, rebooted the device and... stuck in a launcher/app/logo loop...
The phone is Rooted and running Android 6.0.1, I Have ADB access thru the TWRP. Issue here is that no matter what all the commands like: WM, AM, PM result in this error:
CANNOT LINK EXECUTABLE: cannot locate symbol "context_lookup" referenced by "/system/lib64/libandroid_runtime.so"...
page record for 0x7fae83c010 was not found (block_size=64)
Of course I could flash new the phone but the ammount of data and how is configurated right now is worth the effort.
Click to expand...
Click to collapse
silver_ch said:
Hi , do you fix it ?
I have the same problem on my s6
Click to expand...
Click to collapse
Unfortunately not, as CH1N3S3_N00B said gotta do backups when messing with these things!
I needed the phone the next day so hoping google held all my contacts I ended up getting all my data thru adb and then flashing on the new 7.0.1 ROM, TWRP, root and in the end loading up superkernel which allows me to set clock, voltages and governors (just in case is not risky enough that someone might grab the phone and send 2+v to your core )
A side note, if you're gonna flash Nougat watch out that the Xposed thing is not yet avaible, I'm a filthy guy and use modules to hide my status on whatsapp while seeing others and didn't expected that.
Best of luck, keep on breaking stuff up, that's the way to learn, although expensive sometimes!
CH1N3S3_N00B said:
Most likely you will need to reflash.. that's why devs says that you have to do a nandroid backup just in case... Maybe try safemode?(Vol Down after the logo appears)
Click to expand...
Click to collapse
I'm sorry didn't received any notification! anyway if you read my answer below you'll see how it ended :crying: (the safe mode didn't work, it was still trying to boot at 5k)
I used to do a fair bit of modding and participated here a few years ago. Here I am again a little bit wiser and a fair bit behind the times for modding and finding my way around XDA.
My son upgraded his Nexus 6P and gave it to me to play around with. I decided to try modding again and while I have been partially successful, I am now a bit stuck.
I have ADB up and working.
I have TWRP v3.3.0 (?) installed and seemingly working
Following the posted instructions, I installed the statix_angler-20190321-0315-9-v2.0-OFFICIAL image and reboot
Sadly, after showing a coloured G O O G L E which then rotates into a colourful G, it seems to hang (left it over night)
Then, in an attempt to load a different image, I somehow managed to (mistakenly) wipe everything such that the device says there is no OS.
While I can boot to TWRP consistently, I can't seem to get much farther.
When installed via sideload (TWRP) Statix, RR, AOSP get to the logo then all stall.
Much appreciation in advance.
Vicntc said:
I used to do a fair bit of modding and participated here a few years ago. Here I am again a little bit wiser and a fair bit behind the times for modding and finding my way around XDA.
When installed via sideload (TWRP) Statix, RR, AOSP get to the logo then all stall.
Much appreciation in advance.
Click to expand...
Click to collapse
So some progres has been made. After downloading RR-P-v7.0.2-20190422-angler-Official.zip and sideloading, I have a bootable device.
I did get a few E:recv error on uevent messages soi I'm not 100% positive it's working 100%.
I didn't like the icon set of the RR so I'll try a few more and see if I can find a version that can be installed and run properly.
Vicntc said:
So some progres has been made. After downloading RR-P-v7.0.2-20190422-angler-Official.zip and sideloading, I have a bootable device.
I did get a few E:recv error on uevent messages soi I'm not 100% positive it's working 100%.
I didn't like the icon set of the RR so I'll try a few more and see if I can find a version that can be installed and run properly.
Click to expand...
Click to collapse
I might be a **** for assuming, but did you read the op for statix? You used the twrp they have listed in the op, and formatted your data like it tells you to since it uses file based encryption instead of full disk?
Thanks for the responses but this effort is well and truly dead now. The cat came by while the device was USB connected and thought the cord was a plaything. Phone ended up on the floor. Well and truly "bricked" now. Literally. No more ROM fun, just the recycle bin.
Vicntc said:
Thanks for the responses but this effort is well and truly dead now. The cat came by while the device was USB connected and thought the cord was a plaything. Phone ended up on the floor. Well and truly "bricked" now. Literally. No more ROM fun, just the recycle bin.
Click to expand...
Click to collapse
Apparently, "What Is Dead May Never Die" applies to more than the Knights Watch. I was able to get the Nexus 6P back together, charged and booted into TWRP.
Now installing AospExtended-v6.2-OFFICIAL. Guess we'll see if it's really back or not shortly.
Vicntc said:
Apparently, "What Is Dead May Never Die" applies to more than the Knights Watch. I was able to get the Nexus 6P back together, charged and booted into TWRP.
Now installing AospExtended-v6.2-OFFICIAL. Guess we'll see if it's really back or not shortly.
Click to expand...
Click to collapse
If using the StatixOS ROM and get stuck at logo again you might try this per OP for Pie 9.0.
"Install the official ROM, GApps and then wipe your internal data partition.
- THROUGH TWRP
Wipe > Format data
- OR THROUGH FASTBOOT
Code:
fastboot -w"
https://forum.xda-developers.com/nexus-6p/development/rom-statixos-t3832438
Also, per other comment, use the recommended TWRP version. Glad to hear you got the phone back up.
Just to be certain, Bootloader was unlocked, OEM unlocking was checked. ( I rooted the PH1 before and it was simple enough last year but idk what's happing now)
I was on Feb update, wanted to go and apply the patched boot so I can at least apply root. Followed this guide post #7.
https://forum.xda-developers.com/es...ndroid-10-unsupported-unknown-format-t4072429
But when i try to fastboot flash boot <filename>. I get this error "FAILED (remote: Error flashing partition.)"
So I searched some more and discovered this.
https://forum.xda-developers.com/essential-phone/help/flash-twrp-error-flashing-partition-t3834804
And I get the same exact issue in this thread with " FAILED (remote: Flash Write Failure)".
Basically anything to do with wiping fails, and it seems everything wipes first then writes. SO I think i wiped everything I was going to subsequently write but the phone never allowed writing.
Im at a lost in a current bootloader boot loop. Fastboot still recognises the device but further research has me seeing eeprom corrupt chip preventing writing..
Anyone got this fixed? Sorry for the original terrible post... I was a bit in disarray...
Rewrote the OP with more info after i composed myself.
I had a similar issue some time back and writes to either slot would result in failure. Some smaller images would write sometimes. I thought the hardware failed...
But then I read somewhere that bad USB cables can cause issues so although I had used the same 6 ft cable to write many many times, I switched to a short length high quality cable and boom everything was back to normal. No issues since then for 6 months now.
Try it if you have not done so already.
hammer7t said:
I had a similar issue some time back and writes to either slot would result in failure. Some smaller images would write sometimes. I thought the hardware failed...
But then I read somewhere that bad USB cables can cause issues so although I had used the same 6 ft cable to write many many times, I switched to a short length high quality cable and boom everything was back to normal. No issues since then for 6 months now.
Try it if you have not done so already.
Click to expand...
Click to collapse
im cofused as hell. 100% dumbfounded. I had an old rusty usb cable i threw over my wall. I literally went for it and plug it in an old laptop and it worked. Its currently accepting all flashes no errors at all....
wtf. And I tried 3 different brand USB cables as well. Type A to C. and the original C to C. I even used the same cable and same laptop I used to root the device last year but it have errors. I am legit confused. How can the cable work one time and then legit refuse the other. It was eeven a cable recommended on here(or reddit) a long time ago to use WITH flashing and roms etc.
Edit: Phone fully recovered.