Related
Hi guys, my first post here (although have done some reading in the past year) and in dire need of some help. Last night I tried to root my phone. I followed instructions from a sticky post on here, and from another sticky post on another forum.
Before going through how I got there, I'll state what condition my phone is right now, as this may be more reader friendly. I turn on the phone and get the fastboot screen (tricolour). I can reset with call+menu+power. Goes back to bootscreen. Only way to turn off the phone is to remove the battery. If I press trackball+power, a blue LED comes on, the screen stays black. Turning on the phone with camera+power doesn't make a difference. Turning on the phone with home+power doesn't make a difference.
The screen, on turning on, says the following:
'DREA110 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2000
Serial0'
Before it gets to the screen, the screen briefly flashes white and says
'Loading...
No image file!'
I'll try to decribe what exactly I did leading up to this in as much detail as possible, however it took place from 11pm to 4 30 am, and not fully understanding the whys behind what I did, I may not be able to recall it perfectly. Please ask if I haven't provided enough details. I installed the earliest android software and did the telnet commands through telnet, downloaded on the market. I downloaded an app called root.apk and followed the instructions. I got to 'Step 3 - Protect Root' and it said 'Root Protected'. I then got JesusFreke's 1.5 EU rom and renamed it 'update'(.zip) and placed it in my root SD card directory. I loaded the software on. I THINK the mistake I made was not having the radio image (I don't even know what it is or why I need it) before trying to load it. I've since put it on and it hasn't made a difference.
Anyway, I turned on the phone after the install, and it became stuck on the android screen. At this point, home and power and camera and power both worked to provide me with different boot screens when turning on the phone. I did a hard reset. This brings me to where I am now.
Is my phone bricked? I read on a guide here the difference between soft and hard bricking - from what I understood, this seems to be somewhere in between - hopefully if it's a brick it's a soft brick! Any help would be much appreciated, as we all hate to live without our G1's, lol! Looks like I'll be going back to my Nokia 6210 and trying to send this thing for replacement back to T-mobile. Please help guys!
Many thanks
Michael
search around the forums, as far as i know, if you can get to the fastboot, your g1 isn't bricked
Yep, agreed.
In my old G1 days I had the same problem and it was because I didn't have an image file on my SDcard.
You're not bricked but I've since gone from G1 to Hero to Nexus so I'm not what you need to do but it is SIMPLE, I remember kicking myself when I sorted it.
HTH.
thanks for the prompt response guys. Very relieved to hear that it might not be bricked.
I just tried adding two separate image files (one at a time) to the root directory, but it hasn't made a difference. These are the details of what I added:
First I put in all three of these:
Android 1.5
Radio Image ota-radio-2_22_19_26I.zip 9181622 aeecdb49b74a0d4bb67f9d8af70c1889
System Image signed-dream_devphone_userdebug-img-150275.zip 38027127
5ca85a135ff1ddd41643237577cb8ec4
Recovery Image signed-dream_devphone_userdebug-ota-150275.zip 46907411 01c19785eef97b06409f52fed568feff
and then the system image for 1.6 just in case. Is this a noob mistake? I'm very unfamilar with system images, would be really great if someone could link me to the file I should try and put there for the image file!
Thanks again guys
well since it goes into fastboot, is there a way you can flash the recovery in fastboot, and try from there?
sakumaxp said:
well since it goes into fastboot, is there a way you can flash the recovery in fastboot, and try from there?
Click to expand...
Click to collapse
I'd certainly love to try any ideas how I'd do that? If you let me know i'll do it now. atm i'm not aware of any buttoms/commands which work in fastboot, but I've never used it tbh.
yeah to be honest, im not sure how to do that either, i just remember i was lurking around this forum and i saw a previous thread, that had a similar problem and someone mentioned the tip i gave you, so if any senior members or anyone know how to do this, please explain
Tranquility__89 said:
thanks for the prompt response guys. Very relieved to hear that it might not be bricked.
I just tried adding two separate image files (one at a time) to the root directory, but it hasn't made a difference. These are the details of what I added:
First I put in all three of these:
Android 1.5
Radio Image ota-radio-2_22_19_26I.zip 9181622 aeecdb49b74a0d4bb67f9d8af70c1889
System Image signed-dream_devphone_userdebug-img-150275.zip 38027127
5ca85a135ff1ddd41643237577cb8ec4
Recovery Image signed-dream_devphone_userdebug-ota-150275.zip 46907411 01c19785eef97b06409f52fed568feff
and then the system image for 1.6 just in case. Is this a noob mistake? I'm very unfamilar with system images, would be really great if someone could link me to the file I should try and put there for the image file!
Thanks again guys
Click to expand...
Click to collapse
I may be wrong here (if I am come round and strangle the cat).
But I don't see any .img files?
They are all zips? you need to have the image files UNZIPPED an as .img IRC.
OK, I unzipped the folder and put a folder in the root which had the .img files in them.. still didnt work. because i was trying to put them on to the sdcard through my girlfriends old nokia, it was very slow and kept crashing so the only thing is, i didnt manage to get all 3 unzipped folders on there. would that make a difference?
edit: hope I can still work towards fixing it - i need to check if i have a compatible micro sd card reader when i get back from work! please keep any ideas coming
You need the DREAIMG.nbh on your sdcard. Download the DREAIMG-RC29.zip file, unzip, place DREAIMG.nbh in /sdcard, boot into bootloader, and flash.
i did what cloverdale described on a bricked G1 and it worked just fine , now i need to figure out how to get donut on the mobile
anybody? pm if you can help and TIA
cloverdale said:
You need the DREAIMG.nbh on your sdcard. Download the DREAIMG-RC29.zip file, unzip, place DREAIMG.nbh in /sdcard, boot into bootloader, and flash.
Click to expand...
Click to collapse
Thanks for your reply. I'm downloading this one DREAIMG-RC29.zip
I'll then extract on my computer, isolate the DREAIMG.nbh file and copy it into root of SD card.
Is that correct so far
How do I flash?
Many thanks
Hmm, been doing as much research as I can in the time I have, and it appears I need to type command prompts into the fastboot screen? If someone could tell me exactly what to do, that would be a lifesaver, because I am really missing my G1
I didn't think I was this much of a n00b, but apparently so, heh.
bump.. been doing as much research as possible, but most of my net access atm is from work which has many sides blocked (incl XDA!) and im not entirely sure how to do these things that have been suggested.. if someone could just go into a little bit more detail id be really grateful.
Tranquility__89 said:
Thanks for your reply. I'm downloading this one DREAIMG-RC29.zip
I'll then extract on my computer, isolate the DREAIMG.nbh file and copy it into root of SD card.
Is that correct so far
How do I flash?
Many thanks
Click to expand...
Click to collapse
Once you have extracted DREAIMG.nbh and placed it on the sdcard, all you need to do is power on while holding camera, and the installation should begin (or perhaps it asks you to confirm), and not console is needed. Let it do its work, and when it tells you to reboot, press and hold call+menu+end and you will reboot to RC29.
cloverdale said:
You need the DREAIMG.nbh on your sdcard. Download the DREAIMG-RC29.zip file, unzip, place DREAIMG.nbh in /sdcard, boot into bootloader, and flash.
Click to expand...
Click to collapse
And if that doesn't work I would see if your sdcard is fat32
Thanks guys!!!!!!!!!!! it worked! Much thanks indeed.
There is another problem now though, if anyone can help: I'm doing a manual update to 1.5 (rc8) from 1.0 (rc7) and its getting stuck on the G1 screen and not loading.. not hard bricked or anything, can still access recovery and bootloader.. This thread has more information: http://forum.xda-developers.com/showthread.php?t=625677
thanks again
help please
Hi, my g1 is stuck at the seria10 fastboot screen. It is a US g1 that I purchased rooted. I know enough about these sort of things to get myself into trouble. I removed an app (card game) and my phone then got stuck so I did a battery pull. Now all it will do is either spin on the g1 screen or I can get the three skateboards fastboot screen. I am unsure as to what to do now. I downloaded the rc29 build and put it onto my sd card. I am on a mac so I do not think I use FAT32. I thought putting the rc29 on my sd card and holding the power/send/menu key would tell the device to reboot with the rc29 build. Should I have deleted all the stuff of the sd card? I just want my phone to work - I didn't know the phone was rooted until after I had purchased it from a dude off craigslist. any help is appreciated.
sd card is formatted to fat 16 not 32 according to my diskimage. Help?
brian
bcp0809 said:
Hi, my g1 is stuck at the seria10 fastboot screen. It is a US g1 that I purchased rooted. I know enough about these sort of things to get myself into trouble. I removed an app (card game) and my phone then got stuck so I did a battery pull. Now all it will do is either spin on the g1 screen or I can get the three skateboards fastboot screen. I am unsure as to what to do now. I downloaded the rc29 build and put it onto my sd card. I am on a mac so I do not think I use FAT32. I thought putting the rc29 on my sd card and holding the power/send/menu key would tell the device to reboot with the rc29 build. Should I have deleted all the stuff of the sd card? I just want my phone to work - I didn't know the phone was rooted until after I had purchased it from a dude off craigslist. any help is appreciated.
sd card is formatted to fat 16 not 32 according to my diskimage. Help?
brian
Click to expand...
Click to collapse
Disk utility on a Mac will allow you to format to fat32, you must do this. What happens when you power on the phone while holding down home?
I was able to do the home power thing and wiped the handset then rebooted it. Not sure why it worked this time over any previous times...oh well at least it works. Thank you for your prompt reply.
basically, before you guys judge, why would i need a pattern bypass, let me get through the story.
Basically, my tenant couldnt pay her rent, so she decided to give me half and leave. when she left, she also left her dell streak. i gave her a call and she told me i can just have it. when i tried to turn it on, it wouldnt so i charged it. waited a while, say 6 hours, then when i got back to it, there was a pattern lock. called her again but unfortunately, her cell phone line got deactivated. its been 2 days, and ive been trying but no luck.
basically, i just need a program, software, anything? lol. to bypass this because i want to sell it, or maybe try to fall in love with it
*things i have tried*
[1.] Vol up + Power
~brings me to (stock??) recovery (im guessing?) with 5 choices.
0. Boot Up
1. Factory reset (User data only)
2. Software upgrade via update.pkg on SD card
3. Factory reset (User data and Internal Tablet storage)
4. Power off
~Chose #1 which failed
~Chose #3 also failed
both booted up perfectly and still showed the pattern unlock screen.
[2.] Followed a guide
~i basically treated the streak like it was bricked, so i fallowed a guide from illdill (sorry i forgot the link) but it was something related to nvflash and using it to flash images 2-21 on the dell streak 7.
~this method also failed, and also booted up perfectly.
*[3.] Try to put HoneyStreak RC 2.1*
~i get the error "Formatting partition 2 BCT please wait.. FAILED!"
idk what i means but all i know is that when i used the search button, i guess peoples who ask about it and have trouble about it, they get ignored. they try to bump, but yet no response. I read from post 427 to almost 560. none was answered. if there is a way out there. please help me ;(
only 2 methods i tried. anyone else? thanks in advance xda users. quick responses that arent usually nonsense gets a thank button clicked from me
jayjaypops said:
basically, before you guys judge, why would i need a pattern bypass, let me get through the story.
Basically, my tenant couldnt pay her rent, so she decided to give me half and leave. when she left, she also left her dell streak. i gave her a call and she told me i can just have it. when i tried to turn it on, it wouldnt so i charged it. waited a while, say 6 hours, then when i got back to it, there was a pattern lock. called him again but unfortunately, his cell phone line got deactivated. its been 2 days, and ive been trying but no luck.
basically, i just need a program, software, anything? lol. to bypass this because i want to sell it, or maybe try to fall in love with it
*things i have tried*
[1.] Vol up + Power
~brings me to (stock??) recovery (im guessing?) with 5 choices.
0. Boot Up
1. Factory reset (User data only)
2. Software upgrade via update.pkg on SD card
3. Factory reset (User data and Internal Tablet storage)
4. Power off
~Chose #1 which failed
~Chose #3 also failed
both booted up perfectly and still showed the pattern unlock screen.
[2.] Followed a guide
~i basically treated the streak like it was bricked, so i fallowed a guide from illdill (sorry i forgot the link) but it was something related to nvflash and using it to flash images 2-21 on the dell streak 7.
~this method also failed, and also booted up perfectly.
only 2 methods i tried. anyone else? thanks in advance xda users. quick responses that arent usually nonsense gets a thank button clicked from me
Click to expand...
Click to collapse
Try flashing Honeystreak (it completely erases the internal memory since it needs to repartition it) if you like Honeystreak, keep it, if you want stock, flash back. Hopefully that will work.
bluesy_92 said:
Try flashing Honeystreak (it completely erases the internal memory since it needs to repartition it) if you like Honeystreak, keep it, if you want stock, flash back. Hopefully that will work.
Click to expand...
Click to collapse
thanks for quick response, ill try and see, most of the things im reading are, i have to atleast have CWR. which i highly doubt she has. when i tried to explain to her what "rooting" means, lets just say she wasnt interested at all.
unfortunately, it didnt work. somethings about "Formatting partition 2 BCT please wait.. FAILED!" and doesnt go through, that makes method 3 = failed. unless someone out there has a different suggestion?
thanks in advance
Uh...it failed to format the partition? I don't think I've ever seen that happen.
I know this will sound stupid, since you are probably in the right forum, but where you said "streak" are you sure it was the 7 inch and not the 5? Also, you said you got into recovery by volume UP and power, but I think volume DOWN and power is stock recovery...maybe it had CWM installed by someone who has used it before? (the options sound like CWM) and in that case, someone may have changed something. Again, I'm shooting in the dark, but if it is a streak 5, or if it has CWM, it would be different than just a stock Streak 7 on the lockscreen. The streak 5 and 7 are not just different sizes of the same device - they run on a different chipset. The 5 has a snapdragon (I believe) and the 7 has a Tegra 2.
EDIT: You said Streak 7 in the title, so...I'm pretty sure you know it's a 7. In that case, I don't know why it won't flash :-/
bluesy_92 said:
Uh...it failed to format the partition? I don't think I've ever seen that happen.
I know this will sound stupid, since you are probably in the right forum, but where you said "streak" are you sure it was the 7 inch and not the 5? Also, you said you got into recovery by volume UP and power, but I think volume DOWN and power is stock recovery...maybe it had CWM installed by someone who has used it before? (the options sound like CWM) and in that case, someone may have changed something. Again, I'm shooting in the dark, but if it is a streak 5, or if it has CWM, it would be different than just a stock Streak 7 on the lockscreen. The streak 5 and 7 are not just different sizes of the same device - they run on a different chipset. The 5 has a snapdragon (I believe) and the 7 has a Tegra 2.
Click to expand...
Click to collapse
ahhh, thank you. first off, the partition, basically it looks like this (http://forum.xda-developers.com/showpost.php?p=15109690&postcount=425). i have no idea why it fails.
the only ways i could tell it "might be" a streak 7 is....
stock, Volume Up+Power is stock recovery menu. Volume Down+power is USB Fastboot. Has red letters as well.
now. is there anything visible or any button power combo where i would be able to find out if this was a dell streak 5 or 7? sorry for the nweb question.
*fyi, i know how CMW looks like, i have owned many android devices and... lets just say trust me... the Volume Up+Power looks like stock recovery and the only reason i say this is because it has 5 options, and 2 of them are Factory Reset.
Thanks again for quick response!
Other than the screen size, the capacitive buttons are layed out differently. On the streak 5, they are equally spaced, wheras the Streak 7 has them placed so that in landscape, they would all be under your thumb. The Streak 5 also has a removable battery, and the Streak 7 does not. If you check the back and it is smooth with a removable battery, it's a 5. If it is lightly textured without a removable battery, it is a 7.
Hope this helps
EDIT: And as far as the partition, I still don't know what would cause the problem. It might be best to ask someone with more NVFlash experience than me
bluesy_92 said:
Other than the screen size, the capacitive buttons are layed out differently. On the streak 5, they are equally spaced, wheras the Streak 7 has them placed so that in landscape, they would all be under your thumb. The Streak 5 also has a removable battery, and the Streak 7 does not. If you check the back and it is smooth with a removable battery, it's a 5. If it is lightly textured without a removable battery, it is a 7.
Hope this helps
EDIT: And as far as the partition, I still don't know what would cause the problem. It might be best to ask someone with more NVFlash experience than me
Click to expand...
Click to collapse
perfect bluesy_92. you've helped me so much already even thought my dell streak is still "unable to be used" now im for sure guarenteed this is a dell streak 7 (lol) since there is no removable battery and the c buttons are right under my thumb landscape wise.
as for the partition, would you help me figure out? ill sorta spam (not really) on the development thread for anyone who has nvflash experience to help me out with my streak.
as for others who click on this thread and do read and by any chance know any nvflash experience. please do help and just jump right in. thanks so much XDA community providers lets see if we can get through a bypass.
as of things to try
as of things to try in the morning when i wake up for work
the only thing im missing now is my adapter for my miniSD card to stick it in my streak and do the update.pkg file from the stock recovery menu. idk if it will bring me far because at work, i have internet access all day via phone (htc sensation) and i can try to keep update with my xda app but i have no desktop whatsoever.
jayjaypops said:
perfect bluesy_92. you've helped me so much already even thought my dell streak is still "unable to be used" now im for sure guarenteed this is a dell streak 7 (lol) since there is no removable battery and the c buttons are right under my thumb landscape wise.
as for the partition, would you help me figure out? ill sorta spam (not really) on the development thread for anyone who has nvflash experience to help me out with my streak.
as for others who click on this thread and do read and by any chance know any nvflash experience. please do help and just jump right in. thanks so much XDA community providers lets see if we can get through a bypass.
Click to expand...
Click to collapse
Well, I've heard of people getting devices that are locked in read-only, basically making them unable to be flashed. The fact that nothing is working scares me that this may be the case, but at the same time, I never experienced it, so I definately can't be sure. Someone who has may be able to tell you if you're stuck. If it is read-only, your only hope is Dell by that point :-/
That's the first thing I think you should find out. Because if it is locked in read-only, your case is pretty much closed at that point (and not in a good way, unless Dell helps you.) If you find out it's not, then I would try to figure out why Honeystreak isn't flashing properly.
You can try update.pkg - everything is worth a shot, but unlike flashing Honeystreak, I think it won't repartition or anything (updating through a .pkg is the way manufacturers release updates - it was not designed to be harmful to the users data, afaik) so that's not exactly a sure-thing. Don't let that stop you from trying it, though - when something can't be used at all, any idea is a good idea
bluesy_92 said:
Well, I've heard of people getting devices that are locked in read-only, basically making them unable to be flashed. The fact that nothing is working scares me that this may be the case, but at the same time, I never experienced it, so I definately can't be sure. Someone who has may be able to tell you if you're stuck. If it is read-only, your only hope is Dell by that point :-/
That's the first thing I think you should find out. Because if it is locked in read-only, your case is pretty much closed at that point (and not in a good way, unless Dell helps you.) If you find out it's not, then I would try to figure out why Honeystreak isn't flashing properly.
You can try update.pkg - everything is worth a shot, but unlike flashing Honeystreak, I think it won't repartition or anything (updating through a .pkg is the way manufacturers release updates - it was not designed to be harmful to the users data, afaik) so that's not exactly a sure-thing. Don't let that stop you from trying it, though - when something can't be used at all, any idea is a good idea
Click to expand...
Click to collapse
well, im not really trying to flash anything, i dont even care if its rooted or not, i just want it to be working basically. so my son can watch his elmo while i play my game or update my roms or watch my movies without him whining anything just to make it stock perfect again and this bypass to go through >__<"
What happened when you tried nvflash ?
Did it push all of the partitions properly ?
Are you sure you had it in apx mode ?
I just recovered mine from a honeystreak flash and nvflash rewrites all partitions. Then try to fastboot push the system / recovery images.. After that you should be able to use cwm via fastboot to write a new rom ( I went back to streakdroid 1.3 ).
Just put the image file into your fastboot directory and boot it from your computers hard drive ( fastboot boot cwm.img )
pyraxiate said:
What happened when you tried nvflash ?
Did it push all of the partitions properly ?
Are you sure you had it in apx mode ?
I just recovered mine from a honeystreak flash and nvflash rewrites all partitions. Then try to fastboot push the system / recovery images.. After that you should be able to use cwm via fastboot to write a new rom ( I went back to streakdroid 1.3 ).
Just put the image file into your fastboot directory and boot it from your computers hard drive ( fastboot boot cwm.img )
Click to expand...
Click to collapse
re read past posts?
pyraxiate said:
What happened when you tried nvflash ?
Did it push all of the partitions properly ?
Click to expand...
Click to collapse
this is what it looks like when i double click download.bat (http://forum.xda-developers.com/showpost.php?p=15109690&postcount=425) it gives me a FAILED!
pyraxiate said:
Are you sure you had it in apx mode ?
Click to expand...
Click to collapse
hold down Volume up + Volume down while plugging the USB cable in? Pretty sure i am because the first time i got prompted on my computer, i already downloaded the drivers, i just had to direct it to find the drivers, it said APX mode.
pyraxiate said:
I just recovered mine from a honeystreak flash and nvflash rewrites all partitions. Then try to fastboot push the system / recovery images.. After that you should be able to use cwm via fastboot to write a new rom ( I went back to streakdroid 1.3 ).
Click to expand...
Click to collapse
when you double click download.bat, after the img file 14 or 15 goes through, does your command screen suddenly disappear? whats your next step through that?
I flashed using these partition images ( Not the ones in the initial NVflash post) Maybe your image files were corrupted on download. Im glad someone uploaded them in 1 rar to ensure a clean set
Id start over from scratch by using this rar as your c:\Nvflash directory
http://www.multiupload.com/OM0VO9HBO9
See if those make a difference. After Nvflash completes the box will close, its normal. Use the pinhole to reset. From there I just used fastboot ( vol down and power ) to boot into cwm ( i can dropbox the image if you need it ). The command is : fastboot boot cwmimagename.img
from there you can format data/cache/system/dalvik/storage ( mine came back with an error not being able to format a few but try it anyway)
Mount SD card and copy something like the streakdroid zip to it. Using CWM's menus, install a zip from SDcard and choose it. It should run w/o error.
I had the Dell logo only stuck on boot after that , so I went into recovery and formatted user data only . From there it booted right up.
When you boot your streak, does it still boot into the original rom or does it just freeze on the Dell logo?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
pyraxiate said:
I flashed using these partition images ( Not the ones in the initial NVflash post) Maybe your image files were corrupted on download. Im glad someone uploaded them in 1 rar to ensure a clean set
Id start over from scratch by using this rar as your c:\Nvflash directory
http://www.multiupload.com/OM0VO9HBO9
See if those make a difference. After Nvflash completes the box will close, its normal. Use the pinhole to reset. From there I just used fastboot ( vol down and power ) to boot into cwm ( i can dropbox the image if you need it ). The command is : fastboot boot cwmimagename.img
from there you can format data/cache/system/dalvik/storage ( mine came back with an error not being able to format a few but try it anyway)
Mount SD card and copy something like the streakdroid zip to it. Using CWM's menus, install a zip from SDcard and choose it. It should run w/o error.
I had the Dell logo only stuck on boot after that , so I went into recovery and formatted user data only . From there it booted right up.
Click to expand...
Click to collapse
sorry for the late reply, i just barely got home from work. i just bought myself a 2 gig micro sd card, and the adapter to stick the micro sd card in the bigger sd card. im going to try the update.pkg. unfortunate of me, i tried to do it right away but its low battery just my luck. charging the streak 7 right now.
pyraxiate said:
When you boot your streak, does it still boot into the original rom or does it just freeze on the Dell logo?
Click to expand...
Click to collapse
not even, it would boot original rom with the users data still enabled. (the reason i say this is because, the pattern lock is still there) even when i tried the nvflash, it would boot right up to the pattern lock and with the same background she always had.
idea
since i now have an sd card, im going to try the "Restore your DS7" but the only thing thats stopping me is that it requires CWR which i dont have. ill try to work around it since my DS7 is recognized by fastboot and ADB. Also wanted to add another misfortune of mine, she does have debug mode on but fastboot should work rather than ADB. wish me luck.
if anyone has any other suggestions or ideas, please budge in. i dont mind at all. thanks for the help all!
lufc said:
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Click to expand...
Click to collapse
sorry lufc. thanks for moving. i apologize. just stressed out from real life events. arent we all ? aha. thanks and im sorry once again!
jayjaypops said:
since i now have an sd card, im going to try the "Restore your DS7"
Click to expand...
Click to collapse
failed, right when i typed adb devices, it shows my DS7 numbers, but when i type adb shell, i dont get ~# sign back. i get an error: Closed!
here i come nvflash. i shall try you again with the help of "pyraxiate" link he used to restore his DS7. wish me luck!
here i come nvflash. i shall try you again with the help of "pyraxiate" link he used to restore his DS7. wish me luck!
Click to expand...
Click to collapse
failed aswell, after double clicking restore.bat, i let it do its own thing, after it pushes p14.img file, it closes the command box right away, so i used an earring to turn off the device, unplugged from the usb, and yet, it still loads up pefectly with the same wallpaper and still the pattern lock... ughh, this is really frustrating!! ;'(
im trying one last step, before i call dell... (i dont even know if they'll replace this since im not the owner or the buyer of the product. unless they will? let me know)
my last step im taking is, im gonna use nvflash again, but this time im gonna use the WIFI DS7 partitions. hopefully it works. please almight lord! *sniff* begging. wish me luck. ill update
and as you already know what im going to say next, if anyone out there has any suggestions, ideas or plans. please help me out. might help others out in the community. thanks so much in advance
Ok guys ... this is the problem ...:crying:
I have (had) a Droid Bionic running ics leak 232 in Brazil (GSM/UMTS ... thanks to xda developers - "bionic in t mobile" thread).
While messing around with the phone connected to linux (baaad idea) at some point I deleted the bootloader ("happy finger" + lack of knowledge os linux).
Now, my phone doesnt power up and RSD Lite doesnt recognize it when connected but, when I connect it to the PC, a green light lits at the top right corner of the phone and Windows recognize it, at the device manager, as a OMAP4430 USB under TI Board tab. This leads me to think that some kind of life still exists down there or, the hardware is alive and waiting for the right software.
After a long quest for a solution, I found this: "forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-gt-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/index9.html".
Now I think this is the way out of this mess (is the same hardware, OMAP platform from Texas Instrument), if exists any, but this was made for Samsung, by Samsung technicians, and doesnt apply to Motorola. :crying: again.
So, is there anyone who can help me, or have any idea of what can be done (other than trow it away or use it as a paper weight)?
Any help would be most appreciated.
Regards
I saw you haven't had any replies yet. My roommate had a similar problem, he managed to mount his system partition automatically and thought his SD card was partitioned into 10 or more partitions.
So he reformated the mount and had a dead phone right after, said he only got a small white light on his notification light when plugged in.
I didn't get a chance to check it out before he took it to Verizon for a refurb, so sadly I'm not much help. Just thought I'd input anything I knew since you still had an empty thread. Hope it comes back alive!
Sent from my kitchen toaster.
Have you tried using the command line version of moto-fastboot? It might work, but might not work... I think you need to boot into fastboot mode, but I could be wrong... Either way it's worth a try.
Also, does anything happen when you try to hold down the vol+ and VOL- buttons when powering on the phone?
Sent from my XT894 running ICS
its dead
danifunker said:
Have you tried using the command line version of moto-fastboot? It might work, but might not work... I think you need to boot into fastboot mode, but I could be wrong... Either way it's worth a try.
Also, does anything happen when you try to hold down the vol+ and VOL- buttons when powering on the phone?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Thank you for your answer danifunker;
The phone is dead. Pressing buttons does nothing. The only thing that happens is to lit the notification green light at the top right corner of the screen WHEN a plug it in my PC and windows keep telling me this is a unknown device. I unsuccessfully used OMAPFlash, but installing the usb drives that came with it, when I plug it to the PC, windows device manager shows me a new device "OMAP4430 USB" under a new tab "TI Board" , whitch is not recognized by RDS lite or adb or fastboot. Is only recognized by OMAPFlash. If you dont know about OMAPFlash, I found it here http://forum.xda-developers.com/showthread.php?t=1701471 , but this procedure is for a Samsung, witch uses the same platform (OMAP4430), but I dont have the right configurations for the Droid Bionic.
Just the same
chrisp6825 said:
I saw you haven't had any replies yet. My roommate had a similar problem, he managed to mount his system partition automatically and thought his SD card was partitioned into 10 or more partitions.
So he reformated the mount and had a dead phone right after, said he only got a small white light on his notification light when plugged in.
I didn't get a chance to check it out before he took it to Verizon for a refurb, so sadly I'm not much help. Just thought I'd input anything I knew since you still had an empty thread. Hope it comes back alive!
Sent from my kitchen toaster.
Click to expand...
Click to collapse
Thank you for your interest.
If you have any further notice about your roommate problem, please let me know.
And, if you manage to post a reply from your kitche toaster, I am sure you will be able to help in this problem. looking forward for that. :laugh:
pjcw said:
Thank you for your interest.
If you have any further notice about your roommate problem, please let me know.
And, if you manage to post a reply from your kitche toaster, I am sure you will be able to help in this problem. looking forward for that. :laugh:
Click to expand...
Click to collapse
Can you explain exactly how you deleted the bootloader off of the Bionic? Knowing EXACTLY (what you ran, what you typed) what you did will help us help you.
As an aside, I had no idea there was a SGSII-OMAP variant, but I am not big on the Samsung phones, just assumed they've only been using their own SoCs for a while now...
Hi podspi.
Sorry for the delay.
As a matter of fact, wasnt me that bricked the phone. A friend o mine tryed to flash a gelly beam version, and did it via Fastboot,, under Linux (of witch I know almost notingh).
He told me that the problem was that he made:
fastboot erase mbm
and then
fastboot reboot bootloader
and so the bootloader was lost. He missed a step.
Any help will be greatly aprecieted.
Regards
IOW, since the mbm has been erased, and the mbmflashable hasn't been flashed, there is no way to get it into the bootmenu sceen anymore, right?
Hmmm. Let me ask some other folks too.
Sent from my ASUS Transformer Infinity Running Tapatalk.
I wonder if a factory cable would work to get it to flash mode? Why would you even mess with the bootloader trying to install ICS? You do that through recovery, not fastboot.
I was on ICS ... This was an attempt to get it to JellyBeen ... I, also, dont know why. I was perfectly happy with ICS working in GSM/WCDMA. This is why I am so sad ... It was a very stupid thing to do ... As a matter of fact, I will get a factory cable, but I dont think this is gonna help. Anyways, I am keeping it by side to remember me not to mess with things that are working fine. I'm kind of losing hope that it can fixed.
Regards
pjcw said:
I was on ICS ... This was an attempt to get it to JellyBeen ... I, also, dont know why. I was perfectly happy with ICS working in GSM/WCDMA. This is why I am so sad ... It was a very stupid thing to do ... As a matter of fact, I will get a factory cable, but I dont think this is gonna help. Anyways, I am keeping it by side to remember me not to mess with things that are working fine. I'm kind of losing hope that it can fixed.
Regards
Click to expand...
Click to collapse
I think we need to figure out how you flash mbm back onto there. Actually, I think it's mbmloader that you need on there...
mbm = Motorola Boot Manager (?) maybe.
After reading this page: http://omappedia.org/wiki/Bootloader_Project
I believe, mbm = uboot, mbmloader = x-loader
Just found this page... http://www.droid-developers.org/wiki/How_to_load_mbmloader_from_SD_card
download the SBF and grab the mbmloader for ICS. See if you can get a little further...
SamuriHL sHouse of Bionic restored mine when all I could get was fastboot.
Sent from my DROID BIONIC using xda premium
It won't help this. It needs to be flashed at the omap level and since moto isn't about to release the configuration files for the Bionic you can consider this one permanently bricked.
Sent from my Xoom using Tapatalk 2
I tend to agree with SamuriHL. I was thinking that the configuration souldn't be so diferent than others (like Samsung) that uses the same platform (omap). I know that it's naive, but what else could I do. Also, I need the signed files for x-loader and u-boot, of witch I think danifunker is right, this means mbm and mbmloader, that I have, but they came in bin format and not image format (.img). I will try to convert them to .img, but I am at the end of my resources (not that they are so many), and will give up shortly. At this point (giving up), I will buy another cellphone AND IT WONT BE A MOTOROLA, Probably a HTC or a Samsung. But I will keep Bionic at my desktop, as a paperweight, to remind me how I liked it, how I mess things up.
Anyways, if I manage to solve this problem, I will post here, and I wish to thank everyone that spare their time to try to help people. If anyone have any suggestion, I'll be glad to follow.
If you modify them in any way they'll no longer be signed and won't work. Someone else already went through several weeks of trying to fix their phone that had similar issues. He's well connected and still couldn't get the necessary files. Don't necessarily give up on Moto, though...it's not their fault we're stuck with locked bootloaders. Blame VZW for that one. Even Samsung was forced to lock the S3 on VZW. Things may change some day. We'll have to wait and see.
You can always get RAZR i with the unlockable bootloader! that might make things a bit easier...
IT'S DONE!!!!!!!!!
IT'S DONE ....... IT IS ALIVE AGAIN :highfive:
Guys. My phone is alive again. Thanks to FRAGULINA and PICGRABBER for their unvaluable help. It is now running GSM with data enabled (3G) with ICS 232, rooted, thanks to FRAGULINA and HTCFlyerX ( http://forum.xda-developers.com/showthread.php?p=31101192&highlight=build+prop#post31101192).
Well, I'm attaching 2 zip files. One is omapflash and the other is "THE FILES", and instructions on the "release_notes.txt". This works on LINUX.
And works like a charm. Took me (much) less than 5 minutes to get me from a dead phone to bootloader fastboot. And the rest is history. Well known procedures.
Thanks to all of you that helped or tryed to help.
Enjoy.
To those who have an interest in new challanges (as I know you are), i'm opening a new quest and would appreciate your thoughts.
I have at hand an atrix 2 and I want to find where in hell is the subsidy code writen at and how can I read it. This new quest will be at the proper location at the atrix 2 forum.
I think we won this challange. Lets go for another.
Any doubts I am available to help.
Regards.
Holy.....uh, well, WOW! I'm in awe here on this one. WELL DONE!!!!!!!
SamuriHL said:
Holy.....uh, well, WOW! I'm in awe here on this one. WELL DONE!!!!!!!
Click to expand...
Click to collapse
Can we use this method to flash any firmware to the phone? Lets say you load the latest ICS, maybe we use this method which restores the most original bootloader to the phone and then flash to any version?
Which version did you fastboot to?
pjcw said:
IT'S DONE ....... IT IS ALIVE AGAIN :highfive:
Guys. My phone is alive again. Thanks to FRAGULINA and PICGRABBER for their unvaluable help. It is now running GSM with data enabled (3G) with ICS 232, rooted, thanks to FRAGULINA and HTCFlyerX ( http://forum.xda-developers.com/showthread.php?p=31101192&highlight=build+prop#post31101192).
Well, I'm attaching 2 zip files. One is omapflash and the other is "THE FILES", and instructions on the "release_notes.txt". This works on LINUX.
And works like a charm. Took me (much) less than 5 minutes to get me from a dead phone to bootloader fastboot. And the rest is history. Well known procedures.
Thanks to all of you that helped or tryed to help.
Enjoy.
To those who have an interest in new challanges (as I know you are), i'm opening a new quest and would appreciate your thoughts.
I have at hand an atrix 2 and I want to find where in hell is the subsidy code writen at and how can I read it. This new quest will be at the proper location at the atrix 2 forum.
I think we won this challange. Lets go for another.
Any doubts I am available to help.
Regards.
Click to expand...
Click to collapse
This is unbelievable. After talking with you on Gtalk, I thought this was a permanent brick. Thanks for the files...I have a guy on gtalk right now who can benefit from these.
I have no clue what the hell happened. The Note 4 locked up earlier today and refused to reboot at first. Eventually it did come back on. I came home and unplugged it then the screen went black. I figure I bumped the power button getting it, well, apparently not.
I've tried pulling the battery and every button combination. It doesn't do ****. I plugged it in to the PC and found that it shows "QHSUSB__BULK". Did some hunting and apparently that means it isn't totally dead. I found some info here talking about recovering from a brick on the Note 3. Problem is I don't have an unbrick image.
So.... uhh basically what do I do now?
I need a unbrick.img from COD6 so if someone could please help with that. According to the Note 3 thread:
Just run this Unbrick Image Creator in recovery & it'll create "/sdcard/Unbrick_Files" in your internal SD card.
Click to expand...
Click to collapse
That is for the Note 3 so I have no idea if it will make a proper image for the Note 4.
EDIT: According to shabbypenguin that ought to give the proper unbrick image. So can someone here running the COD6 bootloader please run that and upload the file for me?
So for future reference, anyone that may need this can try. I take no credit for this. Most of this is a copy/paste from the Note 3 thread.
What do you need?
DO NOT TRY THIS ON ANOTHER NOTE 4 MODEL WITHOUT THE PROPER UNBRICK IMAGE!
- Hard Bricked Device: T-Mobile Samsung Galaxy Note 4 (N910T)
- Micro SD Card: 4/8/16/32 GB micro SD card
- Unbrick Image: working dump with the same bootloader/version
- Image Writer: native commands on Linux/MacOSx or Win32 Disk Imager on Windows
How to recover?
1- Download Unbrick Image for the COD6 bootloader from here or here
2- If you're using Windows, download Win32 Disk Imager
3- Backup all files on the micro SD card you're using
4- Write the Unbrick Image to your micro SD card using Win32 Disk Imager or Linux/MacOSX commands
5- Remove battery, Insert micro SD card & then the battery
6- Hold Power + Home + Volume Down to enter Download Mode by bootloader on SD card
7- Flash Stock firmware via Odin
YOU MAY NEED TO TEST MICRO SD CARDS WITH DIFFERENT TYPES/SIZES & FORMAT AS EXFAT BEFORE WRITING AN UNBRICK IMAGE ACCORDING TO YOUR BOOTLOADER!
I'd charge it for a while. Take out the battery now and then and try to get into download mode.
DarkStarr said:
I have no clue what the hell happened. The Note 4 locked up earlier today and refused to reboot at first. Eventually it did come back on. I came home and unplugged it then the screen went black. I figure I bumped the power button getting it, well, apparently not.
I've tried pulling the battery and every button combination. It doesn't do ****. I plugged it in to the PC and found that it shows "QHSUSB__BULK". Did some hunting and apparently that means it isn't totally dead. I found some info here talking about recovering from a brick on the Note 3. Problem is I don't have an unbrick image.
So.... uhh basically what do I do now?
I need a unbrick.img from COD6 so if someone could please help with that. According to the Note 3 thread:
That is for the Note 3 so I have no idea if it will make a proper image for the Note 4.
EDIT: According to shabbypenguin that ought to give the proper unbrick image. So can someone here running the COD6 bootloader please run that and upload the file for me?
Click to expand...
Click to collapse
To be honest that has yet to work for anyone. Call up and replace the phone.
10-K said:
I'd charge it for a while. Take out the battery now and then and try to get into download mode.
Click to expand...
Click to collapse
The battery was at 100% it isn't that. It is quite obviously a hard brick. It won't do anything besides show a black screen, no response at all.
BACARDILIMON said:
To be honest that has yet to work for anyone. Call up and replace the phone.
Click to expand...
Click to collapse
Obviously it hasn't helped anyone with a Note 4, we don't have an unbrick image. Now if you're trying to say it hasn't helped anyone, including those with other devices, you're full of crap. This method has unbricked numerous devices that actually have an unbrick image.
If you were not going to help by simply running the file and uploading the results then don't bother responding.
DarkStarr said:
The battery was at 100% it isn't that. It is quite obviously a hard brick. It won't do anything besides show a black screen, no response at all.
Obviously it hasn't helped anyone with a Note 4, we don't have an unbrick image. Now if you're trying to say it hasn't helped anyone, including those with other devices, you're full of crap. This method has unbricked numerous devices that actually have an unbrick image.
If you were not going to help by simply running the file and uploading the results then don't bother responding.
Click to expand...
Click to collapse
Are you not in the note 4 thread.. Why would I give a crap about another device. So again does not exist.
I just ran it for you but have no idea if it will work.
Unzip it to use.
Note4_910T_Unbrick_IMG.zip
Link Removed
I'm curious to know if this works just in case i ever hard brick my note 4. Please update us on if it worked or not OP.
DarkStarr said:
I have no clue what the hell happened. The Note 4 locked up earlier today and refused to reboot at first. Eventually it did come back on. I came home and unplugged it then the screen went black. I figure I bumped the power button getting it, well, apparently not.
I've tried pulling the battery and every button combination. It doesn't do ****. I plugged it in to the PC and found that it shows "QHSUSB__BULK". Did some hunting and apparently that means it isn't totally dead. I found some info here talking about recovering from a brick on the Note 3. Problem is I don't have an unbrick image.
So.... uhh basically what do I do now?
I need a unbrick.img from COD6 so if someone could please help with that. According to the Note 3 thread:
That is for the Note 3 so I have no idea if it will make a proper image for the Note 4.
EDIT: According to shabbypenguin that ought to give the proper unbrick image. So can someone here running the COD6 bootloader please run that and upload the file for me?
Click to expand...
Click to collapse
I think everyone has missed asking the most important question.....
What Rom were you running when this happened?
I don't think you have a hard brick.
---------- Post added at 11:25 PM ---------- Previous post was at 11:24 PM ----------
Hardware failure maybe.
chipworkz said:
I just ran it for you but have no idea if it will work.
Unzip it to use.
Note4_910T_Unbrick_IMG.zip
https://www.androidfilehost.com/?fid=24052804347758591
Click to expand...
Click to collapse
First, thanks for taking the time to run it and upload it. Unfortunately thanks to your unbrick image along with another guys I have determined that either:
A. The phone hates like all of my SD cards
B. Something else is wrong with the device than even just a hard brick.
XBlackChaosX said:
I'm curious to know if this works just in case i ever hard brick my note 4. Please update us on if it worked or not OP.
Click to expand...
Click to collapse
Unfortunately it didn't boot. I think something further is wrong with the device, ie hardware. I do know when plugged in it was showing the "QHSUSB__BULK" when plugged in. When the SD was installed and I attempted to go to DL mode it disappeared so it was trying to do SOMETHING. Again I think it is hardware.
Jammol said:
I think everyone has missed asking the most important question.....
What Rom were you running when this happened?
Click to expand...
Click to collapse
I was running CM12. Whatever the latest nightly was, IIRC 6/10. It was either that or 6/6. I was also running the Xposed for 5.1 6/9 version that fixed it with CM versions after ~ 6/3.
Android_Monsters said:
I don't think you have a hard brick.
---------- Post added at 11:25 PM ---------- Previous post was at 11:24 PM ----------
Hardware failure maybe.
Click to expand...
Click to collapse
I think it was. Even with the unbrick image it wouldn't boot. It did try to do something but I think because of some hardware failure it wouldn't even boot that.
DarkStarr said:
First, thanks for taking the time to run it and upload it. Unfortunately thanks to your unbrick image along with another guys I have determined that either:
A. The phone hates like all of my SD cards
B. Something else is wrong with the device than even just a hard brick.
Unfortunately it didn't boot. I think something further is wrong with the device, ie hardware. I do know when plugged in it was showing the "QHSUSB__BULK" when plugged in. When the SD was installed and I attempted to go to DL mode it disappeared so it was trying to do SOMETHING. Again I think it is hardware.
I was running CM12. Whatever the latest nightly was, IIRC 6/10. It was either that or 6/6. I was also running the Xposed for 5.1 6/9 version that fixed it with CM versions after ~ 6/3.
I think it was. Even with the unbrick image it wouldn't boot. It did try to do something but I think because of some hardware failure it wouldn't even boot that.
Click to expand...
Click to collapse
I definitely suggest just flashing the stock Rom in Odin and then calling in to get a replacement.
Good ole cm12 strikes again.
Pp.
Thats what happens when you venture away from TW to long on a Samsung device! [emoji38] [emoji38] [emoji38]
I have seem to have found the issue and solution to this problem that many of us have been experiencing. If you have encountered issues like myself, there is a thread dedicated to the description of this problem; MAJOR LAG, RANDOM REBOOTS, the phone won't boot up and goes into a screen where you read:
----Mmc_failed failed boot---
After searching for about a month, it seems to be an internal SD issue. Many have reported to having these issues after they root, others upgrading to the non reversible DOK2 FIRMWARE. Others were stock with out root and had this issue as well.
**THE PARTITION OF THE INTERNAL SD CARD IS CORRUPTED**
Could be corrupted files, that stick to the phone EVEN AFTER ODIN FLASHING STOCK MANY TIMES.
(I Odin 5 times back to back to fix and the partition was still corrupted)
People thought "well, if Odin doesn't work, it's a hardware issue" I thought that myself, and it was not.
My friends, I have found something that has worked for me and would like to share with you guys. I hope this fixes your device like it did mine. I've been so close to throwing this Note 4 against the wall, running it over with my car, or smashing it with a hammer. I had no way to return my device as many have suggested to do because I left T-mobile a while back. Plus, rooting my phone voided my warranty. Yada, yada, yada, let's get into it.
*Since the internal partition to the SD card is messing up, we need to repair it.
**In order for this to work, you will need to be ROOTED.
*Download an app called "AParted SD Card Partition." Hope I don't violate any rules, but here is the link to it on Google Play.
https://play.google.com/store/apps/details?id=com.sylkat.AParted
Once the app gains root access, you will be brought to the main screen. Click the tab that says tools. Once that screen pops up, you will see
Part 1 FS: fat32 . Size 31914 MB
Part 2
Part 3
Part 4
Please note that the size to Part 1 may be a different number. That is what mine read.
*You will now click Part 1
*After doing so, at the bottom where it says create, click it and replace it with REPAIR.
*Hit apply, and you're all set.
*Turn off phone, pull battery out for 10 seconds, as well as external SD card and Sim. (They hold small amounts of electric current which may prevent the phone to do a proper boot) I usually hold both volume buttons, power button, home button, and pull the s spen out for 10 seconds simultaneously, then put it all back together and boot up.
*******Also, I used the app to delete the partition, and creating it again to avoid problems from a faulty repair. So if you want to do that, click Part 1. Instead of repair, click delete. Once done, click Part 1 again, then click create. Hit the Fat32, and start it. Once it's created, you shouldn't have issues. In case you're worried, pictures and videos will not be erased.******
I HAVE NO AFFILIATION WITH THE DEVELOPER, BUT HE SAVED MY DEVICE WITH THIS APP. PLEASE, PLEASE, PLEASE DON'T FORGET TO THANK HIM AND HIT THE LIKE BUTTON IF THIS WORKED FOR YOU AS WELL. LEAVE COMMENTS AND QUESTIONS BELOW, AND IF YOU SEE PEOPLE TALKING ABOUT THE PROBLEM IN OTHER THREADS, RE- DIRECT THEM TO THIS THREAD.
This is what I got when repairing the partition. You should have a message as well.
um... if they can't start up the device, how are they going to download it from the play store and install to run it? Thanks!
Are you able to go into DOWNLOAD MODE AND FLASH FIRMWARE? I had the Mmc_failed screen and my phone would not turn on until I took everything out the phone; battery, both cards and s pen, then hold all the buttons down.
Try this to reboot like I described up at top.
Turn the phone off. Pull the battery out, s pen out, SD card and SIM CARD.
PRESS AND HOLD ALL HARDWARE BUTTONS FOR 10 SECONDS WITH EVERYTHING OUT THE PHONE. I CLICK ALL THE BUTTONS SEVERAL TIMES TO GET ANY ELECTRIC CURRENT OUT THE PHONE. IT WON'T BOOT UP IF YOU DON'T DO THAT. I'm assuming it messes with the boot up process. Anyways, Re assemble and boot. When I was having this mmc_failed crap, it would take several times doing these steps so that the phone could boot. Don't get frustrated and try again until it boots up. Sometimes it would sit on the NOTE 4 screen, other times it would boot up to the Android logo with the mmc_failed screen. It takes several attempts since the PARTITIONS TO THE SD CARD ARE CORRUPTED. IF YOU ARE ABLE TO ODIN FLASH FIRMWARE, FLASH THE FIRMWARE TO HELP YOU BOOT UP. FLASH TWRP, THEN ROM, then you will have root.
If you still get the mmc_ boot after repairing it, erase the partition, and create it again. I updated the guide on top on how to do that. Haven't had a single hiccup or Mmc_failed bs since then. Good luck guys.
Please report back if it worked for you.
I will try this as soon as I can. The t-mobile store I went to was unhelpful and only wanted to sell me a new phone, even though I've only had the phone for 1 yr and 1 week. The problems started 2 weeks ago. Thank you for giving me hope.
Sent from my SM-N910T using Tapatalk
mtran1977 said:
I will try this as soon as I can. The t-mobile store I went to was unhelpful and only wanted to sell me a new phone, even though I've only had the phone for 1 yr and 1 week. The problems started 2 weeks ago. Thank you for giving me hope.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
No problem. Save everything important from your sd card and formatt it. That also helps. Try booting up your phone without your sd card. You know what mmc is? An sd card. Google it. Ive seen corrupt sd cards prevent phones from booting up.
Now I can't turn on the phone to fix like you. This morrning I'n in stock DOK2 and have all of error like you. I flash TWRP and flash cook rom, hope can fix like you. But after flash TWRP succesfull, I'm flash cook rom but the phone turn off and can't turn on. when it turn on, it go in to download mode and notice MMcC read fail. I try many time but it still like that. I use odin to load DOK2 Stock firwame but it FAIL. try many time still FAIL
now I don;t know anything need to do to save my phone. lol
What does it fix??
I tried using this application and the first partition that came up was a 61240 Mb partition. I thought it has to be my external SD card. Then i pulled out the external sd card and ran this application again. This time it did not find any partition.
Is this what its suppose to do? If not can you post a screenshot of your partition list.
Thanks
thiennvbk said:
Now I can't turn on the phone to fix like you. This morrning I'n in stock DOK2 and have all of error like you. I flash TWRP and flash cook rom, hope can fix like you. But after flash TWRP succesfull, I'm flash cook rom but the phone turn off and can't turn on. when it turn on, it go in to download mode and notice MMcC read fail. I try many time but it still like that. I use odin to load DOK2 Stock firwame but it FAIL. try many time still FAIL
now I don;t know anything need to do to save my phone. lol
Click to expand...
Click to collapse
After flashing TWRP AND THE COOKED ROM, TURN OFF THE PHONE. TAKE THE BATTERY OUT....SIM CARD OUT...TAKE THE SD CARD OUT AND THE S PEN PUT.
THEN WITH ALL THAT OUT, PRESS AND HOLD POWER FOR 20 SECONDS. THEN TRY TURNING ON THE PHONE. HAD THE SAME ISSUE AND IT TURNED ON AFTER A FEW TRIES.
U may need tp try to do that a few times until you get it to power on.
This is Kinda confusing, we are talking about the INTERNAL STORAGE here, Right? If so, How on earth an App can Format the Internal Storage while its being used obviously by the OS itself? and How can it NOT erase any Media files? It seems very unrealistic approach? unless we boot the system using external boot device then wipe the affected partition, think "Ultimate Boot CD" or "Hiren" for Windows.
What you are saying is like this: Boot Windows laptop/Desktop normally, then Format C: from within Windows !!!
I know you mentioned REPAIR PARTITION, that would/might be OKAY, but to Re-Create the Partition of the MMC (Internal Storage), this sounds crazy, and not even doable.
Please Shed some more lights into this !
It does not fix internal SD
Willy318is said:
This is Kinda confusing, we are talking about the INTERNAL STORAGE here, Right? If so, How on earth an App can Format the Internal Storage while its being used obviously by the OS itself? and How can it NOT erase any Media files? It seems very unrealistic approach? unless we boot the system using external boot device then wipe the affected partition, think "Ultimate Boot CD" or "Hiren" for Windows.
What you are saying is like this: Boot Windows laptop/Desktop normally, then Format C: from within Windows !!!
I know you mentioned REPAIR PARTITION, that would/might be OKAY, but to Re-Create the Partition of the MMC (Internal Storage), this sounds crazy, and not even doable.
Please Shed some more lights into this !
Click to expand...
Click to collapse
If you take out the external SD card, the app does not detect any partition. So this means that we are never fixing the internal memory, just the external one.
rajatkuthiala said:
If you take out the external SD card, the app does not detect any partition. So this means that we are never fixing the internal memory, just the external one.
Click to expand...
Click to collapse
So all of this lengthy post and RED Promises are all BS?
I thought so !
Willy318is said:
So all of this lengthy post and RED Promises are all BS?
I thought so !
Click to expand...
Click to collapse
I am still waiting @notufatjesus to reply.
---------- Post added at 03:09 PM ---------- Previous post was at 02:37 PM ----------
I was wondering, could this issue be related to eMMC like they had on earlier galaxy series. These symptoms are pretty much similar.
created new thread with real solution
Ashwin Prabhunerurkar said:
created new thread with real solution
Click to expand...
Click to collapse
I have the same problem and also hope have a way to repair this error. Now very difficult to use the phone.lol
Mine works fine
@dannygoround
My hopes went up then got nuked as I read the comments lol