Related
Right then,
Already searched on this one and not yet seen a solution to my problem. I own a T-mobile G1 and my phone crashes after it has booted up, or will not boot up properly: either the T-mobile G1 screen stays on for 5-6 seconds then I get a black screen, or it boots up then freezes with a black screen, or it won't switch on at all.
I currently have:
T-Mobile G1 with Root
2.22.19.26I radio installed
1.33.2005 "Death" SPL installed
Amon_RA's RA-v1.2.3 recovery installed
MghtyMax "What a feeling" 1.9.1 Hero ROM installed
fat32, ext3 and linux-swap on class 6 8Gb sdcard
I can get to recovery (sometimes.....it doesn't always get that far) and fastboot, so hopefully it's not bricked. I have already tried wiping (ALT+W) and formatting the ext2 (from the option in RA's recovery menu and also via console); removing all the partitions and starting afresh recreating them (after removing them of course), and as I can get to recovery (sometimes) I have tried flashing a different ROM (SENSEhero 1.3.3 unthemed) but still get the same issue.
I have flashed quite a few ROMs recently and not had any issues, so any help on this one would be most appreciated!
matthenry87 said:
Check your SD Card. My buddy had the same "black screen" problem and I discovered his SD card was slightly popped out. I clicked it back in and boom. problem solved. For him at least!
Click to expand...
Click to collapse
I'll give it a go..........
Seems like it is a problem with the sd card. Removed it and plugged it into my pc via a card reader and it couldn't recognise the card. Amazon here we come! Thanks for the help!
Give us a logcat from ddms.bat.
Binary100100 said:
Give us a logcat from ddms.bat.
Click to expand...
Click to collapse
he already solved it....
Not again......
B-man007 said:
he already solved it....
Click to expand...
Click to collapse
Okay,
It is still doing it and I'm not sure if it is the sdcard. Tried a different card I have at home and I still have the same problem.
I'm also getting extra coloured pixels appear on the T-Mobile G1 screen.
I can still get to bootloader and recovery (sometimes.....).
How do I pull a logcat?
MrZ
adb logcat
you can also run ddms.bat and get the log from there
misterzak said:
Okay,
It is still doing it and I'm not sure if it is the sdcard. Tried a different card I have at home and I still have the same problem.
I'm also getting extra coloured pixels appear on the T-Mobile G1 screen.
I can still get to bootloader and recovery (sometimes.....).
How do I pull a logcat?
MrZ
Click to expand...
Click to collapse
well trying to solve the problem by trying another sdcard is not a fix... since some roms do rely on the ext contents for things to work properly. what i suggest is having the 3nd card completely wiped and partitioned correctly..then move a rom onto the card and flash like u normally would.
Thanks for the info.
That was one of the first things I tried. I managed on Tuesday to install AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2.zip, and it worked for a short period of time, but it now crashes or doesn't boot up.
Getting worried now.......
misterzak said:
Thanks for the info.
That was one of the first things I tried. I managed on Tuesday to install AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2.zip, and it worked for a short period of time, but it now crashes or doesn't boot up.
Getting worried now.......
Click to expand...
Click to collapse
Something may be wrong with the phone itself
Try flashing the RC29 and seeing if the problem persists. if it does, then its probably a hardware problem. You can talk to tmobile or HTC about it and see what they say
B-man007 said:
Something may be wrong with the phone itself
Try flashing the RC29 and seeing if the problem persists. if it does, then its probably a hardware problem. You can talk to tmobile or HTC about it and see what they say
Click to expand...
Click to collapse
Thanks for that. I assume if they ask me to return it to them to reflash the original bootloader and recovery screens so that they cannot tell I've been "playing" with my phone...
Haha well once you flash the RC29 you wont have to because it will all be stock. If Tmo replaces phones for missing text messages, which is for sure a software problem (yes ive seen them do this), then they definitely will for this issue.
B-man007 said:
Haha well once you flash the RC29 you wont have to because it will all be stock. If Tmo replaces phones for missing text messages, which is for sure a software problem (yes ive seen them do this), then they definitely will for this issue.
Click to expand...
Click to collapse
If I flash RC29 (or RC7 for me) will this brick the phone as I currently have Death SPL. I'm sure I've read that somewhere on here?
Unrooted.......
I've now reverted back to RC7 (as I'm in the UK) and all seems okay....for now.
I will run it like this for a day to see if it still crashes or does anything funny. If it doesn't, I will re-root and start again!
Thanks for the help with this. I will update if it continues to crash.
Alright lets hope this fixed it lol
also it may be a little late but you should be fine flashing the RC7 as it replaces the SPL and radio
EVT Board.........
B-man007 said:
Alright lets hope this fixed it lol
also it may be a little late but you should be fine flashing the RC7 as it replaces the SPL and radio
Click to expand...
Click to collapse
Now this is interesting, RC7 was fine. Re-rooted the phone, fine. Flashed AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2.zip ROM, fine. Flashed Amon_RA's v1.2.3.img recovery, fine. This is where it gets fun, partitioned my card within the recovery to FAT32, ext2 and linux-swap, then rebooted into recovery. The phone crashed. So, I thought there must be an issue with the sdcard. Put in the stock 2Gb card with the RC7 DREAIMG.nbh file on and pressed camera+power to go back to RC7. It came up with an red code 00058002, then went back to the bootloader screen. It stated at the top that it was an EVT board. Searched all of the Dream Q&A section for EVT and absolutely nothing. Tried going into bootloader again and that screen started to warp and the graphics and pixels started to jumble up.
Any ideas?
wow.....it changed board types on you?
did you manage to flash cyan at all before that happened?
you should flash cyan and boot on it before flashing amonra's recovery.
you can then flash the recovery then partition the card and wipe just to be safe
B-man007 said:
wow.....it changed board types on you?
did you manage to flash cyan at all before that happened?
you should flash cyan and boot on it before flashing amonra's recovery.
you can then flash the recovery then partition the card and wipe just to be safe
Click to expand...
Click to collapse
I flashed the AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2 ROM and booted it up fully. Then using the Terminal Emulator within Dev Tools I flashed Amon_RA's recovery. All went well until I partitioned the sdcard. It won't boot up at all into the home screen or recovery, just bootloader, although it did this before when it first started crashing. I'm gonna leave it tonight and try again tomorrow.
Do you know anyone else on here who has any idea on this one? Seems like I'm the first!
This is probably an issue with the recovery itself...though ive never read about anything like your having.
ill bump this thread and see if anyone can help...maybe david can (ill tell him to get on here)
why dont you give a differant recovery image and dont try to partition just try with a fat32 sdcard on a cyan rom or something see what happens with that
i've done a lot of searching and haven't been able to figure out why i cannot flash the latest roms. example, i can flash the nightly build 283 but not the most recent 295. the latest miui rom and the GB ones. everytime i try to flash i get E:Can't open /sdcard/xxx (bad). it is really starting to irritate the crap out of me. my boot loader is unlocked, hboot v.0.33.0012, and amon ra 2.0 recovery. i tried partitioning my sd card with 128mb swap, 1024mb ext3, and it hasn't helped any. if anyone has any ideas i would appreciate any help i can get.
easyN1 said:
i've done a lot of searching and haven't been able to figure out why i cannot flash the latest roms. example, i can flash the nightly build 283 but not the most recent 295. the latest miui rom and the GB ones. everytime i try to flash i get E:Can't open /sdcard/xxx (bad). it is really starting to irritate the crap out of me. my boot loader is unlocked, hboot v.0.33.0012, and amon ra 2.0 recovery. i tried partitioning my sd card with 128mb swap, 1024mb ext3, and it hasn't helped any. if anyone has any ideas i would appreciate any help i can get.
Click to expand...
Click to collapse
Rom manager
Sent from my Nexus One using XDA App
switched to rom manager, still no luck, same message...
still don't know why, but i decided to swap my 32gb card for the 4gb that came with the phone, first rom i tried i got an error 7 message, the second finally flashed, so it has something to do with the sd card apparently... i just flashed gingerpassion, i'm going to keep on playing and see if i can figure out what my problem is
Shivammcool said:
Rom manager
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I wish I could say "Nice try, you're getting the hang of this forum thing," but unfortunately you still don't have a clue. This is not an issue that has anything at all to do with ROM Manager (which is really only a frontend to Clockwork Recovery, anyway). PLEASE "lurk more". That is, read posts rather than just making pointless posts. Then you will know a few things and be able to help people out.
(apologies to the OP)
easyN1 said:
everytime i try to flash i get E:Can't open /sdcard/xxx (bad).
Click to expand...
Click to collapse
easyN1 said:
still don't know why, but i decided to swap my 32gb card for the 4gb that came with the phone, first rom i tried i got an error 7 message, the second finally flashed, so it has something to do with the sd card apparently... i just flashed gingerpassion, i'm going to keep on playing and see if i can figure out what my problem is
Click to expand...
Click to collapse
That does certainly sound like an SD issue. I would recommend doing a full format of the 4GB (without doing any partitioning to remove any extra variables), and then trying to flash one of the ROMs that were giving you trouble. If it fails, there is an option under the Other menu in Amon_RA's recovery that will allow you to export the recovery log to your SD card. Do that, and post that log (or even just review it on your own) and we should be able to better determine where the issue lies.
Good luck!
When I bought this Nook a few months back it was shipped with v 1.2. Now that I have messed it up and recovered it I'm on 1.0.1. Is there a way to get back to 1.2?
Also now my Nook says I have no storage. I have no books downloaded, it's just after the factory reset.
It says there is no storage because you are not on 1.2 or above. Just update manually through BN.
---------------------------------
Sent from my LG Optimus V using Tapatalk
koopakid08 said:
It says there is no storage because you are not on 1.2 or above. Just update manually through BN.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. My problem is now that when I connect the Nook to the computer (linux Ubuntu), two drives show up both named B&N eReader. Neither can be opened. I suspect it's due to the fact that it shows no storage. How do I go about upgrading through B&N?
Maybe I have to use Windows? The 1.2 version before I started tinkering was recognised by Ubuntu Linux. Any help so I don't get murdered by my 9 year old for breaking her Nook is appreciated.
So are you on 1.2 now? Try making a bootable clockwork card and flashing this.
http://forum.xda-developers.com/showthread.php?t=1050520
---------------------------------
Sent from my LG Optimus V using Tapatalk
koopakid08 said:
So are you on 1.2 now? Try making a bootable clockwork card and flashing this.
http://forum.xda-developers.com/showthread.php?t=1050520
---------------------------------
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
No I'm not on 1.2. I used to be but after "bricking" it and bringing it back I now have 1.0.1. I also have a bootable clockwork sd card. My question was how to get to 1.2 or 1.3 and you answered it by the link. Than you very much. I love you guys
loveubuntu said:
When I bought this Nook a few months back it was shipped with v 1.2. Now that I have messed it up and recovered it I'm on 1.0.1. Is there a way to get back to 1.2?
Also now my Nook says I have no storage. I have no books downloaded, it's just after the factory reset.
Click to expand...
Click to collapse
It would help us more if we knew what you did/tried to do when messing it up... was it one of the "restore nook to stock" cwr images you used?
Try using the 8 failed boot attempts.... if you haven't messed up your recovery partition it should restore you to the version that was originally installed on your NC.
To help troubleshoot and fix it is really helpful to tell us what happened... you could also try using the cwr restore to stock 1.2 or the cwr update to 1.2 or 1.3 files.
DizzyDen said:
It would help us more if we knew what you did/tried to do when messing it up... was it one of the "restore nook to stock" cwr images you used?
Try using the 8 failed boot attempts.... if you haven't messed up your recovery partition it should restore you to the version that was originally installed on your NC.
To help troubleshoot and fix it is really helpful to tell us what happened... you could also try using the cwr restore to stock 1.2 or the cwr update to 1.2 or 1.3 files.
Click to expand...
Click to collapse
Thanks for your reply DizzyDen. As I mentioned in the post before yours, I think I'm all OK now. I had made a bootable CM7 sd card to have stock/CM7 (without and with SD) but somehow had CWR installed on the emmc.
Then trying to upgrade to 1.3 from their website, I was not allowed. So what I had to do was to make a bootable CWR sd card, boot from the sd card and remove the CWR from emmc (used a flashable zip found on forums) and then flash a 1.0.1 image. Then I used the 1.2 update from the above link to update to 1.2 and then used the 1.3 from B&N website to upgrade to 1.3. Now I'm where I want to be but thinking about rooting again It's too much excitement but didn't have to be.
I think I must have tried to flash CWR recovery with the ROM Manager app when I had the CM7 bootable sd card in that caused all these problems. It's nice to have the bootable CWR though.
loveubuntu said:
When I bought this Nook a few months back it was shipped with v 1.2. Now that I have messed it up and recovered it I'm on 1.0.1. Is there a way to get back to 1.2?
Also now my Nook says I have no storage. I have no books downloaded, it's just after the factory reset.
Click to expand...
Click to collapse
You can get you Nook back to the factory 1.2 by following procedure the it described near the end of the first post at
http://forum.xda-developers.com/showthread.php?t=1054027
Look for the "Complete Wipe" heading.
BASIC! said:
You can get you Nook back to the factory 1.2 by following procedure the it described near the end of the first post at
http://forum.xda-developers.com/showthread.php?t=1054027
Look for the "Complete Wipe" heading.
Click to expand...
Click to collapse
thanks, i wonder why this isn't included in the guide sticky thread. Also, is there a simpler way to complete wipe than the 8 reboot sequence? a script?
loveubuntu said:
thanks, i wonder why this isn't included in the guide sticky thread. Also, is there a simpler way to complete wipe than the 8 reboot sequence? a script?
Click to expand...
Click to collapse
Here's a BootCnt file and a dos batch file that will make it a LOT easier for ya if you have adb running...
DizzyDen said:
Here's a BootCnt file and a dos batch file that will make it a LOT easier for ya if you have adb running...
Click to expand...
Click to collapse
Thank you. I have adb and will give it a whirl later. I'm still stcuk with trying to have a working ROM on the nook. The Phiremod7.1 which is based on CM7 seems to be working fine now but I can't get any CM7 nightlys to show any soft keys at the bottom, hence no back or notification bars. I'm going to try a stable one to see if that maybe the problem. Funny that I was able to run the nightlies when I was off of SD.
Also while I have your ear, , I'm a bit confused about this wiping and rooting business with the nook. I'd appreciate any help for me to understand it a litlle better. Excuse my ignorance.
Why can't a complete wipe be performed when booted from a CWM sd card? In the numerous phones I have rooted the sequence is easy: root, install custom recovery, nandroid back up, wipe data/system/cache/dalvik and then install a new rom. In the nook,, I still get residual from the last rom (my wifi settings, wallpaper, B&N registration info) unless I do the 8 reboot sequence. What does the 8 reboot wipe that we can't wipe any other way? What does emmc format accomplish then?
Also, how is it that I can install a rom through an SD card without ever rooting the nook?
TIA
loveubuntu said:
Thank you. I have adb and will give it a whirl later. I'm still stcuk with trying to have a working ROM on the nook. The Phiremod7.1 which is based on CM7 seems to be working fine now but I can't get any CM7 nightlys to show any soft keys at the bottom, hence no back or notification bars. I'm going to try a stable one to see if that maybe the problem. Funny that I was able to run the nightlies when I was off of SD.
Also while I have your ear, , I'm a bit confused about this wiping and rooting business with the nook. I'd appreciate any help for me to understand it a litlle better. Excuse my ignorance.
Why can't a complete wipe be performed when booted from a CWM sd card? In the numerous phones I have rooted the sequence is easy: root, install custom recovery, nandroid back up, wipe data/system/cache/dalvik and then install a new rom. In the nook,, I still get residual from the last rom (my wifi settings, wallpaper, B&N registration info) unless I do the 8 reboot sequence. What does the 8 reboot wipe that we can't wipe any other way? What does emmc format accomplish then?
Also, how is it that I can install a rom through an SD card without ever rooting the nook?
TIA
Click to expand...
Click to collapse
I have only recently noticed the remnant effect of previous data... I suspect it has something to do with B&N's newest software effecting the ability to wipe the partitions... perhaps formatting the partitions first would assist.
The 8 failed boots completely re-initializes the Nook with the factory backup data stored on mmcblk0p3... there is the complete rom and device specific backup stored in zip files there.
You can install a ROM by booting off the SD because B&N set our nooks up to boot from SD first... so when you do nothing from the Internal storage is loaded upon boot... so its not in use and can easily be manipulated.
I know this is a common thing, as I searched before coming to the conclusion that I had to create my own thread about this topic. However, everyone says to re-flash to stock, which is what caused this problem for me. I had a huge error with the phone, and after 2 weeks of flashing, I am able to get it to this stage where it will boot up, but after booting up, the screen turns black, but the bottom buttons light up, and can be pressed, but no action.
I can access recovery and download mode. Odin recognizes my phone. I can charge with phone off (the battery image shows it charging.)
Here is the thread where I discussed my issues if you care to learn more about my issues (it was a dbdata error).
androidforums.com/samsung-galaxy-s/567335-factory-reset-wont-fix-galaxy-s-infinite-boot-mode.html
Anyways, now there is no errors (no red lines during recovery mode). But I have no idea what to do.
No one has a clue? This really sucks, I've spent so much time trying to fix it when all along it can't really be fixed it seems.
Try flashin to Stock i897ucKK4.... http://forum.xda-developers.com/showthread.php?p=18370912
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
Try flashin to Stock i897ucKK4.... http://forum.xda-developers.com/showthread.php?p=18370912
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I've tried that. With that rom it boot loops and gives me a dbdata error.
Edit. Just tried again and after the att screen during boot up it gives me different variations of this screened like a grainy type of image. I snapped a pic below. I tried going into recovery and it gave me the same image on the screen.
Imgur.com/qyo5P.jpg
U need to flash the KK4 WITH the GB Bootloaders.
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
U need to flash the KK4 WITH the GB Bootloaders.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
(I've tried that as well, and I tried it again)
After flashing it booted in recovery, and tried to do the wipes.
Failed to mount /sdcard (I/O error) -- (There's no SD card inside, so that's probably why)
E:copy_dbdata_media: can't mount /sdcard your storage not prepared yet, please use UI menu format and reboot actions.
--Wiping data
Formatting /data...
Formatting/dbdata...
Formatting /cache...
Data wipe failed.
Then I tried a wipe data/factory reset. And this time it said Data wipe completed.
Then when I rebooted it said
Failed to mount /data (invalid argument)
And then it said another error but it was in yellow, so I didn't really catch it.
And it boot loops.
[Thank you for attempting to help me by the way!]
Do a search in the Q & A forum for the dbdata error that you are getting. This has happened before to several persons and i do remember that there were a few threads on this already.
U probably are going to have to flash a stock firmware (that is contained in a .tar file) through regular Odin3 v1.83 (or similar). This Odin is Not a "one click". Make sure the .tar file for the stock contains the dbdata.rfs file and also don't use the pit file. See if that works. --- The i897ucKF1 in the Dev forum would be a firmware that comes to mind that has all u need. Quick search should lead u to that one.
If successful, u should be able to flash up to KK4 afterwards or go to Dev Roms if u want.
4-2ndtwin said:
Do a search in the Q & A forum for the dbdata error that you are getting. This has happened before to several persons and i do remember that there were a few threads on this already.
U probably are going to have to flash a stock firmware (that is contained in a .tar file) through regular Odin3 v1.83 (or similar). This Odin is Not a "one click". Make sure the .tar file for the stock contains the dbdata.rfs file and also don't use the pit file. See if that works. --- The i897ucKF1 in the Dev forum would be a firmware that comes to mind that has all u need. Quick search should lead u to that one.
If successful, u should be able to flash up to KK4 afterwards or go to Dev Roms if u want.
Click to expand...
Click to collapse
I've tried 3 different roms with Odin3 v1.85. (that contain dbdata.rfs in the tar)
Maybe with that rom I'll have better luck. I searched for that rom at samfirmware and downloaded it. I searched in the dev forum, and all I got was an odin one click for that rom, and you said to do the regular version.
I flashed it, and it gave me the same error as before. With the data wipe failed and other errors. Then when it boots, it boot loops only the att logo.
Att logo, darkness for a second. Then repeat.
Also. I've done numerous searches for the words I'm getting, and every one says to flash back to the kk4 stock rom, but that's what causes the problems for me.
Is there anyone that can help at this point?
Is it possible that I have messed up partitions on the internal SD card? I found a way to fix that, but its for the HTC incredible. Any ideas on a captivate version of this thread?
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/#entry56396
albokid2468 said:
Is there anyone that can help at this point?
Is it possible that I have messed up partitions on the internal SD card? I found a way to fix that, but its for the HTC incredible. Any ideas on a captivate version of this thread?
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/#entry56396
Click to expand...
Click to collapse
Have you tried this one yet? http://forum.xda-developers.com/showthread.php?t=731989
This is probably the best restore rom I know of, it will flash eclair bootloaders so you will have to reflash gingerbread bootloaders before you flash any current roms.
If this doesn't do it then it sounds like you may have a bad spot in the memory module itself, possibly a bad transistor in the circuit. You may need some advanced help from a technician, I don't know if any of these jtag guys have advanced diagnostics but it wouldn't hurt to check it out.
As a last resort, you may have to send it in to Samsung.
crt60 said:
Have you tried this one yet? http://forum.xda-developers.com/showthread.php?t=731989
This is probably the best restore rom I know of, it will flash eclair bootloaders so you will have to reflash gingerbread bootloaders before you flash any current roms.
If this doesn't do it then it sounds like you may have a bad spot in the memory module itself, possibly a bad transistor in the circuit. You may need some advanced help from a technician, I don't know if any of these jtag guys have advanced diagnostics but it wouldn't hurt to check it out.
As a last resort, you may have to send it in to Samsung.
Click to expand...
Click to collapse
I've tried that one. That is one of the few where it will give no errors, however it boots up to a black screen. I believe that was the state I was in when I started this thread, with that rom.
Is the memory module or the transistor in the circuit located on the main board of the device. I was thinking of buying a logic board (mother board) and replacing it with a new one.
Although at this point, I got the Galaxy S3 so this phone isn't really a necessity at this point.
albokid2468 said:
I've tried that one. That is one of the few where it will give no errors, however it boots up to a black screen. I believe that was the state I was in when I started this thread, with that rom.
Is the memory module or the transistor in the circuit located on the main board of the device. I was thinking of buying a logic board (mother board) and replacing it with a new one.
Although at this point, I got the Galaxy S3 so this phone isn't really a necessity at this point.
Click to expand...
Click to collapse
Hi bro, have you solved your problem? Eager to hear from you cause I am having the excat same trouble.....
qaler2010 said:
Hi bro, have you solved your problem? Eager to hear from you cause I am having the excat same trouble.....
Click to expand...
Click to collapse
Look here: http://forum.xda-developers.com/showthread.php?p=39614278#post39614278
BWolf56 said:
Look here: http://forum.xda-developers.com/showthread.php?p=39614278#post39614278
Click to expand...
Click to collapse
Thks for your reply
I am not new to captivate, I have already had it for nearly 2 years, and everything including odin ways that used to work now doesn't....
So strange, yesterday it was ok as usual ,but when I got up this morning and it couldn't light up the screen no matter what physical button I hit. So I did flashing but it results in nothing.
Use I897UCJF6-final-OCD-REV0 and my phone can boot up but screen comes black during boot animation
Use 3FileKF1NOBOOT or JF6_secure, my phone just gets stuck on the first boot screen
Use custom recovery, then (E:failed to mount /data (file exists) E:delete_data_files: can't mount /data your storage not prepared yet, please use ui menu for format and reboot actions)
So sad now...I haven't backed up my data and for now it looks like I could never get it back...
qaler2010 said:
Thks for your reply
I am not new to captivate, I have already had it for nearly 2 years, and everything including odin ways that used to work now doesn't....
So strange, yesterday it was ok as usual ,but when I got up this morning and it couldn't light up the screen no matter what physical button I hit. So I did flashing but it results in nothing.
Use I897UCJF6-final-OCD-REV0 and my phone can boot up but screen comes black during boot animation
Use 3FileKF1NOBOOT or JF6_secure, my phone just gets stuck on the first boot screen
Use custom recovery, then (E:failed to mount /data (file exists) E:delete_data_files: can't mount /data your storage not prepared yet, please use ui menu for format and reboot actions)
So sad now...I haven't backed up my data and for now it looks like I could never get it back...
Click to expand...
Click to collapse
Try using Odin KK4 with bootloaders. JF6 is really outdated.
BWolf56 said:
Try using Odin KK4 with bootloaders. JF6 is really outdated.
Click to expand...
Click to collapse
Thanks again for your quick reply.
//Now I have only found one kk4 with bootloader download link in hotfile.com, which is currently not banned in my country...
So would you please be that kind to post another download link like in mediafire, dropbox or googled docs?
But I don't really think it is the problem of being outdated or not, JF6 and that I said above worked fine before...
FYI, I was using Slim 4.2.2 build 2.5 when I got the trouble, maybe there is something special I don't know when downgrading to GB?
Regards!
--------
Found the link:http://www.mediafire.com/?zqpip6uac4n7ov7
qaler2010 said:
Thanks again for your quick reply.
Now I have only found one kk4 with bootloader download link in hotfile.com, which is currently not banned in my country...
So would you please be that kind to post another download link like in mediafire, dropbox or googled docs?
But I don't really think it is the problem of being outdated or not, JF6 and that I said above worked fine before...
FYI, I wasing using Slim 4.2.2 build 2.5 when I got the trouble, maybe there is something special I don't know when downgrading to GB?
Regards!
Click to expand...
Click to collapse
JF6 is Froyo, not GB. Therefor, you're flashing the wrong bootloaders. You need the GB bootloaders, hence why I'm telling you to use KK4.
As for links, the only one I have is: http://hotfile.com/dl/137865417/4bc...S_Bootloaders_Re-partition_Full_Wipe.zip.html - Which is hotfile.com and I can't upload it to my db at work.
BWolf56 said:
JF6 is Froyo, not GB. Therefor, you're flashing the wrong bootloaders. You need the GB bootloaders, hence why I'm telling you to use KK4.
As for links, the only one I have is: http://hotfile.com/dl/137865417/4bc...S_Bootloaders_Re-partition_Full_Wipe.zip.html - Which is hotfile.com and I can't upload it to my db at work.
Click to expand...
Click to collapse
Pretty sure not the issue of bad flash after odining KK4...
I start to believe corrupted, or even worse, dead internal storage causes all the hell....
qaler2010 said:
Pretty sure not the issue of bad flash after odining KK4...
I start to believe corrupted, or even worse, dead internal storage causes all the hell....
Click to expand...
Click to collapse
Sorry but this isn't very clear.. Did you manage to flash Odin KK4 with bootloaders? Did it say complete and reboot the phone? If so, what exactly happened and what exactly did you do?
Hi.
Firstly, i should start by apologizing for my stupidity and complete failure to be less... useless, when it comes to my phone.
I am selling my Galaxy note, which is rooted and has ICS Stunner 2 on it, with 'cwm-based recovery v6.0.2.7 (if that helps)
My issue is, Before selling my phone I took out my 'external SD' card and decided to reformat/nuke my internal SD, thinking that the firmware would remain intact and the thing would still be useable if i repartitioned it or whatever.. Again, a bit new to this..
Anyhow, half way through formatting the internal SD the process was interrupted. I can boot the phone, but when I do anything that requires use of the internal SD (saving photos, downloading apps... and in cwm recovery, even factory reset) it wont work
In fact, when I try a factory reset it says 'Error mounting /sdcard/.android_secure
I would love to know what I am meant to do to fix this, and of course am willing to provide any info you may need to help me out here..
As i was typing this the phone got sold and I am now running against the clock to make this work...
please, help!
Thank you so much and I again apologize.
AceS
Quick edit: Kernel version -cm-enhanced+
[email protected] #1
Stunner version 2.2.4
Baseband N7000XXLR1
AceSLive12 said:
Hi.
Firstly, i should start by apologizing for my stupidity and complete failure to be less... useless, when it comes to my phone.
I am selling my Galaxy note, which is rooted and has ICS Stunner 2 on it, with 'cwm-based recovery v6.0.2.7 (if that helps)
My issue is, Before selling my phone I took out my 'external SD' card and decided to reformat/nuke my internal SD, thinking that the firmware would remain intact and the thing would still be useable if i repartitioned it or whatever.. Again, a bit new to this..
Anyhow, half way through formatting the internal SD the process was interrupted. I can boot the phone, but when I do anything that requires use of the internal SD (saving photos, downloading apps... and in cwm recovery, even factory reset) it wont work
In fact, when I try a factory reset it says 'Error mounting /sdcard/.android_secure
I would love to know what I am meant to do to fix this, and of course am willing to provide any info you may need to help me out here..
As i was typing this the phone got sold and I am now running against the clock to make this work...
please, help!
Thank you so much and I again apologize.
AceS
Quick edit: Kernel version -cm-enhanced+
[email protected] #1
Stunner version 2.2.4
Baseband N7000XXLR1
Click to expand...
Click to collapse
If you are selling your note, maybe the best thing you can do is flash stock rom for you region and thats it.
It will solve your problems at once.
djoni_gitara said:
If you are selling your note, maybe the best thing you can do is flash stock rom for you region and thats it.
It will solve your problems at once.
Click to expand...
Click to collapse
I appreciate this, however I have advised the buyer that I am selling it Rooted.
I don't want to let him/her down at all.
Other than this the phone is perfect.. As soon as this is fixed all will be good
Flash a Philz ICS kernel (zip version in recovery) Reboot back into recovery and /Format emmc.
Sent from my GT-N7000 using xda app-developers app
shoey63 said:
Flash a Philz ICS kernel (zip version in recovery) Reboot back into recovery and /Format emmc.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
+1
Forgot about that, that would do the trick:good:
djoni_gitara said:
+1
Forgot about that, that would do the trick:good:
Click to expand...
Click to collapse
You guys are both lifesavers; thanks to you both.
Mods/admins? Delete/lock thread?
AceSLive12 said:
You guys are both lifesavers; thanks to you both.
Mods/admins? Delete/lock thread?
Click to expand...
Click to collapse
Think they won't it will be open for people which have similar problems like you
TheNoticer said:
Think they won't it will be open for people which have similar problems like you
Click to expand...
Click to collapse
Ah of course - Thank you again everyone
I can get some sleep now