Database Users

Stuck at G1 Splash (Help Please)

As a disclaimer, I have already searched and found some people with the same issue. What I haven't found is someone that arrived at this problem in the same way I did. I am scared ****less of bricking my phone (and hope I haven't already). So at this point, I am looking for some help to figure out my best course of action.
I recently updated to JF1.5 using his updater app, and everything worked. Today when I received my new SDcard, I started the process to get apps on my SD following this tutorial: http://forum.xda-developers.com/showthread.php?t=512743
I got as far as partitioning my card using the Apps2SD application as described, doing everything the tutorial says. I began the partition on my phone, and let it sit.....and sit, and sit. It sat frozen on the partitioning screen (the one with the slider to select the size) for almost an hour before i pulled the battery. I selected 1444mb for the ext2 after reading that it was not a good idea to go higher than 1500mb.
Now, as stated the phone boots to the G1 splash and goes nowhere. I am however still able to boot in recovery mode using Home+Power. Interestingly, it says at the top:
"Android system recovery utility
Build: JFv1.42"
Not sure if this means that 1.5 didn't install correctly or what, but that's what it says.
I have no idea what to do at this point, and am scared to go on without some candid advice. Sorry for the noobishness of my description - if there is anything else needed to give accurate advice please let me know. Also thanks in advance for any help I can get!

Same thing happened to me, you have to reflash. I tried using that method and it never worked for me, although I already had the partition. So reflash jf 1.51 and you are golden. BTW that text you see in recovery is the recovery image version, until you switch to another it will say that.

meoshe said:
Same thing happened to me, you have to reflash. I tried using that method and it never worked for me, although I already had the partition. So reflash jf 1.51 and you are golden. BTW that text you see in recovery is the recovery image version, until you switch to another it will say that.
Click to expand...
Click to collapse
Thanks for the response. I'll have to find a way to get that image onto my SD card. I just bought a 16BG card and that was the card I was using when I ran into this problem.....oh wait a sec....
I'm assuming that the JF1.51 update.zip will still be on my old 1GB card from when I updated to JF1.51 via his updater app last week? If so then my life will be a lot easier, and I'll just swap back to that card, boot up in Recovery, flash from update.zip, and that should be it?
Just want to make sure before I put that old card back in and try to flash....

try wiping before you update? Also to mount your SDcard (if you need to) press alt-x in recovery (or in adb shell) and type
Code:
echo /dev/blockl/mmdblk0 > /sys/devices/platform/usb_mass_storage/lun0/file

x2 that's what i had to do since my computer stopped reading sd cards.

Wipe then update.
I'd also recommend using CMv3.4 because the apps2sd is automated. It runs a2sd by itself
And with Cyanogen Recovery v1.2 you can move apps to sd card

First off, just want to thank everyone for the help. I successfully reflashed with jf1.51, but now I can't seem to sign in. I'm on the welcome screen, skipped the tutorial, entered my Gmail account and it sits for awhile trying to contact the server and then says there's a problem with the service or my sim card.
I know my sim card is provisioned for data, so not sure what's happening here...any ideas?
EDIT: Forgot I had to enter the Rogers APN settings, trying that now (Duhhh)
Abolfazl said:
Wipe then update.
I'd also recommend using CMv3.4 because the apps2sd is automated. It runs a2sd by itself
And with Cyanogen Recovery v1.2 you can move apps to sd card
Click to expand...
Click to collapse
I'm interested in this Cyanogen stuff, but no idea where to start. Any good tutorials? I was following this scene for awhile but kinda lost touch a few months ago - turns out there's been lots of developments.

t3mp3st said:
First off, just want to thank everyone for the help. I successfully reflashed with jf1.51, but now I can't seem to sign in. I'm on the welcome screen, skipped the tutorial, entered my Gmail account and it sits for awhile trying to contact the server and then says there's a problem with the service or my sim card.
I know my sim card is provisioned for data, so not sure what's happening here...any ideas?
EDIT: Forgot I had to enter the Rogers APN settings, trying that now (Duhhh)
I'm interested in this Cyanogen stuff, but no idea where to start. Any good tutorials? I was following this scene for awhile but kinda lost touch a few months ago - turns out there's been lots of developments.
Click to expand...
Click to collapse
It is pretty cut and dry. Cyanogen's Mod unleashes the G1 to its max. Apps2sd is automated and is working before you can even turn your phone on.
CMv3.4
CM Recovery v1.2

Abolfazl said:
It is pretty cut and dry. Cyanogen's Mod unleashes the G1 to its max. Apps2sd is automated and is working before you can even turn your phone on.
CMv3.4
CM Recovery v1.2
Click to expand...
Click to collapse
Cool, I guess I'll try it out now before trying to restore everything. I don't see a tutorial for it though, or am I to just follow the previous "How to root" tutorial and just use his image as the update.zip?

t3mp3st said:
Cool, I guess I'll try it out now before trying to restore everything. I don't see a tutorial for it though, or am I to just follow the previous "How to root" tutorial and just use his image as the update.zip?
Click to expand...
Click to collapse
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img

alritewhadeva said:
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
Thanks a lot, going to try that now with my 16GB card. And just to be clear (last questions in this thread, I PROMISE!), I should flash with CM3.4 and THEN install the recovery image, or vice versa?
Also, with CM3.4, will I have to go through to steps again to try to partition my card (which is where i ran into the problem from post #1), or is there some automatic process built into his super-de-duper ROM?
Thanks again to all for the speedy responses!!

t3mp3st said:
Thanks a lot, going to try that now with my 16GB card. And just to be clear (last questions in this thread, I PROMISE!), I should flash with CM3.4 and THEN install the recovery image, or vice versa?
Also, with CM3.4, will I have to go through to steps again to try to partition my card (which is where i ran into the problem from post #1), or is there some automatic process built into his super-de-duper ROM?
Thanks again to all for the speedy responses!!
Click to expand...
Click to collapse
Don't worry asking questions is good as long as they are intelligent. You should flash CM3.4 and then the recovery image, as that is what i did. However, i don't think it really matters. To be safe, flash CM3.4 and then the recovery image.
And to your question pertaining to partitioning your SDcard, you can try MarcusMaximus' Apps2SD2 app which formats the card for you here
Unzip it to your sdcard and install it using ASTRO file manager or some other file manager.
If you have adb working,
Code:
adb install AppstoSD2.apk
if you have other questions you can always contact me on AIM- roflzbrianxdd

alritewhadeva said:
Don't worry asking questions is good as long as they are intelligent. You should flash CM3.4 and then the recovery image, as that is what i did. However, i don't think it really matters. To be safe, flash CM3.4 and then the recovery image.
And to your question pertaining to partitioning your SDcard, you can try MarcusMaximus' Apps2SD2 app which formats the card for you here
Unzip it to your sdcard and install it using ASTRO file manager or some other file manager.
If you have adb working,
Code:
adb install AppstoSD2.apk
if you have other questions you can always contact me on AIM- roflzbrianxdd
Click to expand...
Click to collapse
Thanks a ton, I'll get to this right after i finish this delicious sub! I'll also add you so I can IM if i have any more questions..

t3mp3st said:
Thanks a ton, I'll get to this right after i finish this delicious sub! I'll also add you so I can IM if i have any more questions..
Click to expand...
Click to collapse
Cool, Best of Luck with the flashing

alritewhadeva said:
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
Alright...I successfully partitioned my card, flashed with CM 3.4, but now when I try this instruction to install the new recovery, i get this error msg in Terminal:
error writing recovery: Permission denied
Any ideas?

You have to enter su before the code..
Code:
su
then
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img

meoshe said:
You have to enter su before the code..
Code:
su
then
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
I did not enter the su, I will try that now thanks. In the mean time I also performed this step:
13. My /system/sd is read only and/or didn't upgrade to ext3!
Your filesystem is probably corrupt. Boot into recovery and open a console. Run "mount /system" then "/system/bin/e2fsck /dev/block/mmcblk0p2" and fix your filesystem. Reboot.
from: http://forum.xda-developers.com/showthread.php?t=518851
So I hope that didn't hurt anything...ill try with the su now. Thanks!
edit: out of curiosity, what does the "su" stand for? I feel if I know this it may help me to remember to enter it before any commands.
edit #2: does it stand for "Super User" to allow super user permissions? I gathered this after entering SU prompted me to allow superuser access

New recovery.img successfully installed! Thanks again to everyone that helped me with this.
I know I can transfer apps to SD easily from recovery now, but is there also a similar way to do it from the phone (or do they install to the SDcard by default now?)

Hey T3MP3ST... how did it go with upgrade to cm3.4
I had the same problem as you mentioned start of the post....
(stuck at g1, after partition).
this cm3.4 sounds like the solution for me to have apps2sd..
as it is in the ROM automatically, if i understood correctly.

dynamisoz said:
Hey T3MP3ST... how did it go with upgrade to cm3.4
I had the same problem as you mentioned start of the post....
(stuck at g1, after partition).
this cm3.4 sounds like the solution for me to have apps2sd..
as it is in the ROM automatically, if i understood correctly.
Click to expand...
Click to collapse
Hey there, with the help from everyone in this thread, along with the partitioning instructions using Ubuntu (if you still need to partition your card) from tubaking182 found here: http://forum.xda-developers.com/showthread.php?t=523648, It was great.
I just finished flashing with that ROM and then installing CM's recovery image (which is AWESOME...trackball selection, Apps2SD in one click)
I HIGHLY recommend it. If you have any problems, I'm sure you'll find most of the answers in this thread. If not, try PMing one of the helpful respondents, or I may be of SOME help with some minor questions or assurances.

Fresh Start

So i had to Odin back to stock because in whatever rom i used i wouldnt get vibration for text messages. This worked fine and i flashed back to eugenes stock jk2 that was prerooted. Now i need to install new roms again and im having trouble. I have rom manager installed and superuser was already there. I got the rom on the sd card (tried with multiple roms), but when i go to flash the roms it fails because it can't verify the signature. Even when i go to fix permissions and reboot my phone like rommanager tells me to it cant flash a new rom. On the other roms i had i would just go to advanced options in recovery and disable verification checks but with the stock recovery i cant do this. So my main question is why isnt this option in cwm recovery and how can i get it there so i can start getting roms again. Thanks for anyone who takes the time to read this...

Make sure that you have CWM recovery flashed onto your phone using odin. Also make sure that whatever rom you install is on agreement with your software version.
Sent from my overclocked Fascinate using XDA App

yea maybe i need to try one of eugenes roms because its his froyo version? i have cwm because i installed it through rom manager (well at least i think i have it)

lavcoles said:
So i had to Odin back to stock because in whatever rom i used i wouldnt get vibration for text messages. This worked fine and i flashed back to eugenes stock jk2 that was prerooted. Now i need to install new roms again and im having trouble. I have rom manager installed and superuser was already there. I got the rom on the sd card (tried with multiple roms), but when i go to flash the roms it fails because it can't verify the signature. Even when i go to fix permissions and reboot my phone like rommanager tells me to it cant flash a new rom. On the other roms i had i would just go to advanced options in recovery and disable verification checks but with the stock recovery i cant do this. So my main question is why isnt this option in cwm recovery and how can i get it there so i can start getting roms again. Thanks for anyone who takes the time to read this...
Click to expand...
Click to collapse
Are you putting the rom on the internal memory?

Yea i copied it to the iternal sd, i see it on the internal sd, but the only way to reflash it is to rename it update.zip becauae all i can do is reinstall system packages

You have to download cwmrecovery, plug your phone in while in download mode and put cwmrecovery onto your phone. Just installing rom manager doesn't cut it and trying to flash anything will give the exact errors you're talking about.
Sent from my SCH-I500 using XDA App

how do you delete the post ?

So i put the cwm recovery in the phone slot in odin and reflash it?

lavcoles said:
Yea i copied it to the iternal sd, i see it on the internal sd, but the only way to reflash it is to rename it update.zip becauae all i can do is reinstall system packages
Click to expand...
Click to collapse
You put the rom Just on the internal sd card not any folders right?

its doesent matter at least for me if the rom is right there or in a folder no difference just file called update.zip need to be there (not in the folder )

and no ! u cant flash clockwork recovry thru odin ! loL both of these program u mentioned are intended to flash roms not to be flashed as rom p u can flash in clockwork recovery if the rome is made for it which would be packed with .zip file if its odin file it would be .tar not every rom is flashable thru odin or clockwork depends how devs made it

bartek25 said:
its doesent matter at least for me if the rom is right there or in a folder no difference just file called update.zip need to be there (not in the folder )
Click to expand...
Click to collapse
Something must have gotten corrupted in the file transfer. I know your fustrated . Have you tried repeating the odin process?

Yea it was on the internal sd, i mean iv probably flashed 20 different roms and i know how to move them between different file folders and how to access them ect... The only problem is basically that im stuck in stock which has a different recovery

nomadrider123 said:
Something must have gotten corrupted in the file transfer. I know your fustrated . Have you tried repeating the odin process?
Click to expand...
Click to collapse
No this sounds like a good idea though, maybe i should use a different tar file.

lavcoles said:
Yea it was on the internal sd, i mean iv probably flashed 20 different roms and i know how to move them between different file folders and how to access them ect... The only problem is basically that im stuck in stock which has a different recovery
Click to expand...
Click to collapse
Here is the update.zip that will flash you into clockwork from stock recovery. Put this on your phone's internal sd, reboot to recovery, and hit "reinstall packages". If your phone reboots to stock recovery again, hit reinstall packages again and the second time it should put you right into Clockwork Recovery. Good Luck.

Thank you this is what iv been looking for

NP Friend, let me know if it works for you.

Br1cK'd said:
NP Friend, let me know if it works for you.
Click to expand...
Click to collapse
wow it still says i cant flash the .zip file for some reason, it gives me the same error message about signature verification. I am rooted and i even rerooted but it didnt make a difference, thanks for trying to help though

lavcoles said:
wow it still says i cant flash the .zip file for some reason, it gives me the same error message about signature verification. I am rooted and i even rerooted but it didnt make a difference, thanks for trying to help though
Click to expand...
Click to collapse
What rom are you currently running, still on Eugene's JK2? If you Odin'd a stock file, you may have 2e recovery, not the modded 3e. Check this thread, it may help you out with the stock recovery issue. In fact untermensch mentions this kind of issue specifically in the OP. http://forum.xda-developers.com/showthread.php?t=833423

Br1cK'd said:
Here is the update.zip that will flash you into clockwork from stock recovery. Put this on your phone's internal sd, reboot to recovery, and hit "reinstall packages". If your phone reboots to stock recovery again, hit reinstall packages again and the second time it should put you right into Clockwork Recovery. Good Luck.
Click to expand...
Click to collapse
I just added this to the ACS, thanks for reminding me

[Q] Clockworkmod recovery disappears after reboot

I have looked through all clockworkmod recovery topics, but it seems I am the only one with this issue?
I have a US Xoom wifi-only, HMJ37, with an official 3.1 OTA. Yesterday I unlocked my Xoom, flashed the latest Recovery image(but also a previous version) of CWM. Then I typed fastboot reboot and I could get into the CWM recovery. Nice, no problems. Then I rebooted again, everything works fine and my Xoom works fine. Then I reboot again in recovery and I suddenly get the stock Android Recovery! I flashed it again and the same problem, after the first reboot I have CWM. Reboot to android and reboot again in recovery and I get the stock Android recovery again!
Who knows what is going wrong here? What am I doing wrong or what can this be?

If you flashed CWM 3.2.0.0, that may be your problem. Look at this thread > http://forum.xda-developers.com/showthread.php?t=1074979
Note in the last several pages that some posts were having the same problem as you. I flashed back to 3.0.2.8, and it solved my problem.

Thanks cam30era, I thought I have tried 3.0.2.8 already but I will give it a try this evening and let you know.

olafski72 said:
I have looked through all clockworkmod recovery topics, but it seems I am the only one with this issue?
I have a US Xoom wifi-only, HMJ37, with an official 3.1 OTA. Yesterday I unlocked my Xoom, flashed the latest Recovery image(but also a previous version) of CWM. Then I typed fastboot reboot and I could get into the CWM recovery. Nice, no problems. Then I rebooted again, everything works fine and my Xoom works fine. Then I reboot again in recovery and I suddenly get the stock Android Recovery! I flashed it again and the same problem, after the first reboot I have CWM. Reboot to android and reboot again in recovery and I get the stock Android recovery again!
Who knows what is going wrong here? What am I doing wrong or what can this be?
Click to expand...
Click to collapse
Without a rooted boot.img if will keep deleting The recovery. You can also delete the recovery-boot.p file from the system folder to stop it.
Sent From My Evo

olafski72 said:
Thanks cam30era, I thought I have tried 3.0.2.8 already but I will give it a try this evening and let you know.
Click to expand...
Click to collapse
Bwcorvus is right.
Sent from my ADR6300 using Tapatalk

I have flashed with 3.0.2.8, with my Xoom rooted. Again, the first attempt was succesfull, I came into the CWM menu. I rebooted again to Android. Rebooted with the Sirius Fastboot in Recovery, but there it was again, the stock recovery!
I have not deleted the recovery-from-boot.p since that sounds kind of scary? What can go wrong? When I delete it, that will stop the stock recovery and bring me into the CWM recovery?
Someone also told me I need a SDcard. Is this true and what should I do with it then? The img is on my PC in the same folder as the ADB tools. So why should I need the SDcard for then?

You must have a SD card for CWM.
Sent from my Xoom using Tapatalk

Thanks. So I don't need to do anything with it? Just stick it in there? Do I need to format it in some way? The SDcard is not supported in 3.1 yet, is it? I need the Tiamat kernel for it. But I cannot flash without the CWM. Or just stick it in there and flash recovery again? Which I did and again the first time it worked, after reboot it did not anymore and I am back to stock recovery.
When I reboot with Sirius to recovery, I still need USB debugging on but I do not need to attach it to my PC with the USB cable? I have tried it all, but just need to know to this ;-)
And what about deleting(renaming) recovery-from-boot.p ? Is it safe?

olafski72 said:
Thanks. So I don't need to do anything with it? Just stick it in there? Do I need to format it in some way? The SDcard is not supported in 3.1 yet, is it? I need the Tiamat kernel for it. But I cannot flash without the CWM. Or just stick it in there and flash recovery again? Which I did and again the first time it worked, after reboot it did not anymore and I am back to stock recovery.
When I reboot with Sirius to recovery, I still need USB debugging on but I do not need to attach it to my PC with the USB cable? I have tried it all, but just need to know to this ;-)
And what about deleting(renaming) recovery-from-boot.p ? Is it safe?
Click to expand...
Click to collapse
You need the Tiamat kernel to be able to access the SD card from the OS, once it's booted. But you can access the SD card from CWM without the Tiamat kernel, although I don't know what good it would do you. If you really want to use this thing, you should root and install the Tiamat kernel.
There are lots of threads in the development section which will help you. Make sure that you read the appropriate thread(s) for your type of Xoom, and your country. If there is anything that you don't understand, be sure to ask questions in the appropriate thread.

cam30era said:
You need the Tiamat kernel to be able to access the SD card from the OS, once it's booted. But you can access the SD card from CWM without the Tiamat kernel, although I don't know what good it would do you. If you really want to use this thing, you should root and install the Tiamat kernel.
Click to expand...
Click to collapse
I want to install the language pack and the Tiamat kernel. If I need to flash recovery again and again, this is quite annoying. I just want it to work ;-)
There are lots of threads in the development section which will help you. Make sure that you read the appropriate thread(s) for your type of Xoom, and your country. If there is anything that you don't understand, be sure to ask questions in the appropriate thread.
Click to expand...
Click to collapse
I have looked, but did not find the same problem yet.
And what about renaming recovery-from-boot.p ? I read other topics about it as well, but still anxious to do so.

olafski72 said:
I want to install the language pack and the Tiamat kernel. If I need to flash recovery again and again, this is quite annoying. I just want it to work ;-)
I have looked, but did not find the same problem yet.
And what about renaming recovery-from-boot.p ? I read other topics about it as well, but still anxious to do so.
Click to expand...
Click to collapse
We have a misunderstanding. You need to root your Xoom and install a Tiamat kernel to get SDCard support. You need to refer to the appropriate thread(s) in the development section to do this. You need to find a thread that is for your country, your type of Xoom (3g+wifi, or wifi only), and the version of Honeycomb that is currently running on your Xoom (3.0 or 3.1). Hope this helps.
Sent from my Xoom using Tapatalk

We have a misunderstanding. You need to root your Xoom and install a Tiamat kernel to get SDCard support.
Click to expand...
Click to collapse
Hm, I have copied the language pack zip file on my sdcard(via my PC and my X10 phone :-D ) and then put it back in my Xoom. I have not the Tiamat kernel yet. This is a Xoom US wifi version, HMJ37, it came with 3.0 but I got 3.1 OTA(although I live in the Netherlands). Then I flashed CWM and rebooted in recovery. I choose to install zip from SDcard and the language pack.zip was there. With CWM I probably CAN browse on my SD without the Tiamat. I installed and rebooted. Unfortunately it got stuck in the animation screen. I rebooted (power button and vol up button) and when Motorola logo showed I pressed vol down. I came in the stock recovery again and did a factory reset. This worked fine and it reboot again. When I went through the wizard succesfully, it surprised me too that the language pack was succesfully installed. I have a Dutch version now and finally a Dutch dictionary for my keyboard. And I am very happy.
Since I have put the Tiamat kernel on my sdcard as well, I could flash the Tiamat kernel the same way. I can flash CWM again(AGAIN!) and install the ZIP from the SD like I did with the language pack. But I am a bit scared to do so.... yet

You need to follow the instructions in this thread > http://forum.xda-developers.com/showthread.php?t=1078019
Read the OP, and make sure that you fully understand it. If you have questions, be sure to ask them on that thread. If you decide to proceed, be sure that you understand and follow EXACTLY each step. No shortcuts.
Also, you should not go any further if you can not afford (emotionally or financially) to brick your Xoom. While it is unlikely to happen, you must accept that it could happen before you proceed.
Good luck.

Thanks, I will look at the thread. I think I have all requirements (3.1, root, wifi only, us model) to do it. But I certainly will have a look. I don't wanna brick my Xoom and go boom.

I have just read this link you posted, but this is about rooting?! I have unlocked and rooted my 3.1 already like this. With a different root tool, but in the same way. That is not the issue. The issue is that I can(!) flash CWM and the first(!) time I reboot I can(!) enter CWM and do all you can in CWM. After I reboot again and go to recovery, the stock Android recovery is back.
The only thing I want is the Tiamat kernel now. It is on my sdcard. So I will flash CWM one more time, reboot into recovery again, and then flash the tiamat kernel into it. But I am in doubt whether I should. I will sleep over it.
Bu the main problem, as mentioned in topic subject, is that CWM will(!) install succesfully and starts the first time, but disappears after the first reboot (in CWM).

Sorry, I didn't understand from your previous posts that you were rooted. Follow the instructions in the OP for the Tiamat 1.4.4 kernel thread.
Sent from my Xoom using Tapatalk

No problem, Thanks for all your help. In here the same problem is described: http://forum.xda-developers.com/showthread.php?t=761398
Although in here the problem is a Nexus and no Xoom. But they also talk about renaming this file bwcorvus mentioned in the first page. But like I already asked a few times what the risks are of deleting this file? A shame bwcorvus does not answer anymore, maybe he knows? That would then solve the CWM issue.
For the Tiamat flash, I will have a look at the thread.
Thanks again for all your help!

You could do a nandroid backup (in CWM) and then delete the file. If things go badly, you should be able to boot into recovery and restore.
Sent from my Xoom using Tapatalk

That is a good one. But I was just thinking, after the second reboot CWM disappears, so I can't restore
I have to think about this.

olafski72 said:
No problem, Thanks for all your help. In here the same problem is described: http://forum.xda-developers.com/showthread.php?t=761398
Although in here the problem is a Nexus and no Xoom. But they also talk about renaming this file bwcorvus mentioned in the first page. But like I already asked a few times what the risks are of deleting this file? A shame bwcorvus does not answer anymore, maybe he knows? That would then solve the CWM issue.
For the Tiamat flash, I will have a look at the thread.
Thanks again for all your help!
Click to expand...
Click to collapse
There can be no problems from removing it. If you are truly scarred just rename it rec.bak. Its just a text file that runs at boot to make sure the recovery is stock. If its not, it makes it stock.
Sent From My Evo

[URGENT] Unable to boot after modifying build.prop

Hello,
I was modifying build.prop, had made a backup and saved it in another folder in my phone, after modifying, I think it's because I've forgotten to set permissions or something, now I'm unable to bootup after rebooting.
Any idea how do I solve this? I've read online something about adp or something, but I've totally no clue about these.
Is there anyone who has a solution to this?
With sincerity
Xituc

If you did a backup and have TWRP, just delete the old build.prop in /system, move the backup there and set permissions. ;

This_Guyse said:
If you did a backup and have TWRP, just delete the old build.prop in /system, move the backup there and set permissions. ;
Click to expand...
Click to collapse
I don't have it anymore I think, went to recovery mode, thought I could solve it by resetting by clearing data etc
How do I solve it now?

Xituc said:
I don't have it anymore I think, went to recovery mode, thought I could solve it by resetting by clearing data etc
How do I solve it now?
Click to expand...
Click to collapse
System, data, internal sd, cache, what did you wipe? If you:
1. Wiped data/system :- you can only flash a new rom since you don't know ADB. Or flash stock via odin.
2. Internal sd :- that's it, flash stock firmware via odin.

This_Guyse said:
System, data, internal sd, cache, what did you wipe? If you:
1. Wiped data/system :- you can only flash a new rom since you don't know ADB. Or flash stock via odin.
2. Internal sd :- that's it, flash stock firmware via odin.
Click to expand...
Click to collapse
How do I do that? Is there a way I can skype you or something? Sorry, really needed help!

Xituc said:
How do I do that? Is there a way I can skype you or something? Sorry, really needed help!
Click to expand...
Click to collapse
Which options did you wipe in your recovery?

radicalisto said:
Which options did you wipe in your recovery?
Click to expand...
Click to collapse
I just clicked wipe factory reset smth along those lines.

Xituc said:
I just clicked wipe factory reset smth along those lines.
Click to expand...
Click to collapse
Either reflash your custom ROM via TWRP (dirty flash and it'll keep your data etc) or do a stock flash via ODIN and start again. Can't remember if you can use ADB to restore your build.prop been an age since I used an N3.

radicalisto said:
Either reflash your custom ROM via TWRP (dirty flash and it'll keep your data etc) or do a stock flash via ODIN and start again. Can't remember if you can use ADB to restore your build.prop been an age since I used an N3.
Click to expand...
Click to collapse
My computer doesn't have my device in device manager when I've connected it, was unable to try using ADB earlier when I've tried, any idea why?
Anyway, can you direct me to a guide way I can do a stock flash via ODIN? I'm seeing so many threads in this forum but I've no idea which one is suitable for my phone.
Thanks!!

Xituc said:
My computer doesn't have my device in device manager when I've connected it, was unable to try using ADB earlier when I've tried, any idea why?
Anyway, can you direct me to a guide way I can do a stock flash via ODIN? I'm seeing so many threads in this forum but I've no idea which one is suitable for my phone.
Thanks!!
Click to expand...
Click to collapse
If you were using stock then you'll need to have a read around general and learn how to flash with ODIN. It's pretty straight forward, you can grab official ROMs from either here on XDA or Sam mobile/firmware. The link escapes my mind currently.
If you were using a custom ROM, download to your PC and use ADB Side load or download to your External SD Card and flash via recovery.
You can use THIS for ADB drivers, it's 15second ADB install and it should work for you.

radicalisto said:
If you were using stock then you'll need to have a read around general and learn how to flash with ODIN. It's pretty straight forward, you can grab official ROMs from either here on XDA or Sam mobile/firmware. The link escapes my mind currently.
If you were using a custom ROM, download to your PC and use ADB Side load or download to your External SD Card and flash via recovery.
You can use THIS for ADB drivers, it's 15second ADB install and it should work for you.
Click to expand...
Click to collapse
Weird, computer won't have my phone's device show up...
EDIT:
In the development section, I see lots of roms, any idea which one should I download? I just want one which I can flash to and get my phone working again.
Thank you! I'm on SN-N9005 btw!
Can I contact you via skype or something btw?

Xituc said:
Weird, computer won't have my phone's device show up...
EDIT:
In the development section, I see lots of roms, any idea which one should I download? I just want one which I can flash to and get my phone working again.
Thank you! I'm on SN-N9005 btw!
Click to expand...
Click to collapse
For Stock you'll need the ROM for your region, this is quite important otherwise it causes headaches. For custom, it's entirely up to you, you can choose any TouchWiz based (stock look and feel - I personally recommend AllianceROM by @sparky b for TW based) Or AOSP based (Pure Android with no Samsung features - Temasek's ROM is stellar in this department and the new OMNIROM for the Note 3 will be superb once the dev has it sorted 100%, it's still being debugged and beta tested currently and dev tree's etc redone, stop by @jakew02's thread and have a read at where he is up to)
If you have the N9005 you'll be OK to use any custom ROM for that device. Just stay away from the Exynos (N900) ROMs as they won't work and will brick your phone.
I've recommended a couple of ROMs which are both Stable and feature filled plus one which will be great once fully flying. Other ROMs in the development section are just as great, however, I can only comment on the two I used solidly when I had my Note, and the one's I have ran on other devices. But ultimately it's your choice.

Wifi and sim card not working

So recently I was having some fun with magisk modules. I was on pixel experience 11 plus and all worked fine but then I found a module for some photo processing . After reboot it started to boot loop. I wasn't worried it already happened couple of times. I did my buckup and reinstalled the rom. I did all good but I lt keeps on boot looping. I installed stock miui and it worked but the second it turned on it says android setup isn't responding. I couldn't turn on the wifi, sim card wasn't reading so I tried again to install pixel experience but it's the same thing. Can't use my phone and I tried a lot of things. Is there any way to repair this manually? Like copying some files?. Plzzzz help

What did you do already?
You messed your system. Make a full wipe, partiton and install stock rom.
When I had samsung it was caused by modem - you can try to flash only some modules, but it will take some time to sort things out

yaro666 said:
What did you do already?
You messed your system. Make a full wipe, partiton and install stock rom.
When I had samsung it was caused by modem - you can try to flash only some modules, but it will take some time to sort things out
Click to expand...
Click to collapse
I did all the wipes and yet nothing worked or I did it wrong.
Ive heard about this modem or nhlos files or something like that but I don't really know where to search for this stuff.
Ive rooted my phone to install root explorer. Now I know that installing another Rom wouldn't change anything and instead I have to find a right file to flash or copy. I will do an update if anything works. Thanks for respond

Corgar39 said:
I did all the wipes and yet nothing worked or I did it wrong.
Ive heard about this modem or nhlos files or something like that but I don't really know where to search for this stuff.
Ive rooted my phone to install root explorer. Now I know that installing another Rom wouldn't change anything and instead I have to find a right file to flash or copy. I will do an update if anything works. Thanks for respond
Click to expand...
Click to collapse
When switching ROM, you should Format Data, not just wipe (not the same thing in TWRP) - you can still do it now.
And flash the tgz MIUI firmware by XiaoMiFlash, not just the zip firmware by TWRP. Or, at least flash also the vendor zip firmware

zgfg said:
When switching ROM, you should Format Data, not just wipe (not the same thing in TWRP) - you can still do it now.
And flash the tgz MIUI firmware by XiaoMiFlash, not just the zip firmware by TWRP. Or, at least flash also the vendor zip firmware
Click to expand...
Click to collapse
I already used miflash for tgz and I did format data now I'm looking for different solutions

Corgar39 said:
I already used miflash for tgz and I did format data now I'm looking for different solutions
Click to expand...
Click to collapse
In not sure is it maybe in dtbo. Search the Net and if you have backup of dtbo, try with restoring

zgfg said:
In not sure is it maybe in dtbo. Search the Net and if you have backup of dtbo, try with restoring
Click to expand...
Click to collapse
Tried it. Didn't work unfortunately://

Corgar39 said:
Tried it. Didn't work unfortunately:// I don't think it's repairable
Click to expand...
Click to collapse