ive benn doing my own builds of cm 10 for my i9300 for about 3 weeks and haven't hag any problems with it, i purchased a N7 at the weekend and thought i would do my own build for this device too, i got the proprietary files from github.com/themuppets and placed the in the vendor folder just like i had done with my i9300. my build finishes with no errors, but when i've flashed it and try to boot i get the google logo then it flashes and doesn't get any futher (no boot animation). any advice would be appreciated.
Related
I successfully rooted my Tab from ICS to JB 4.1.2 a few days ago and it has been working fine. It suddenly froze in GMail app this evening. Held down power and attempted reboot. All fine until several revs of the CyanogenMod circle then it froze for a few seconds and then blank screened and rebooted with the Samsung Galaxy Tab 10.1 logo before going back to the CyanogenMod circle. Only stops the looping if I power from the mains. Battery is at about 55% and charging.
I have CWM-based Recovery v6.0.1.5 and I installed JB from cm-10-20121112-EXPERIMENTAL-p4wifi.zip
Can anyone help? I'm new to rooting etc..
Many thanks,
Stuart
Try booting into recovery and doing a full wipe of everything.
Sent From My GalaxyClass StarShip
Thanks
SouthPhilly said:
Try booting into recovery and doing a full wipe of everything.
Sent From My GalaxyClass StarShip
Click to expand...
Click to collapse
Many thanks for the reply SouthPhilly. It didn't work
There seemed to be a problem with formating /data. It just stopped when I tried it. Also stopped if I tried restore. The good news is that I did eventually overcome the problem by following qbking77's excellent info on
How to Unroot / Unbrick the Samsung Galaxy Tab 10.1 - Latest at www dot youtube dot com/watch?v=KYBs98R9rTs with file info at
www dot qbking77 dot com/samsung-galaxy-tab-1012.html
which results in a stock original unrooted GT-7510. From there I rooted back into CWM recovery and reflashed CM10 so I'm back with a working version of 4.1.2
I hope this info may help others unfortunate enough to get stuck like me.
I'm now happy again.
Best wishes to all.
Stuart G3SNA (QTHR)
Well perhaps not quite so happy!
For some strange reason I could not get the USB port to work. It did with my first attempt at flashing to CM 10 - JB 4.1.2 days ago but not now. I have tried all ways several times so eventually I returned to the qbking77 version of the stock 3.2, copied my CWM backups back to the sdcard, then reinstalled CWM recovery and restored from the backup. I now have what appears to be a fully working tab with USB connectivity running 4.0.4 ICS again. I'll stay with this untill JB gets a bit more stable. You never know, pink pigs may fly and Samsung may issue an OTA update :laugh:
Why didn't you flash a nightly instead of a ROM thats dated last month? The latest one runs fine on my p7510
http://get.cm/?device=p4wifi
Sent from my GT-I9100
I didn't know where to find the nightly files when I first did the root and rom flash. I just followed the links I could find using google. The whole thing looked good to start with and I ran it for the best part of a week before it froze up on me. I learned a lot in the last few days and now feel confident in what I'm doing. I did download last night's nightly this morning and flashed the rom. When I connected the usb cable to my pc failed to connect so I reverted to my original zip file thinking the nightly had an issue. Low and behold the usb cable connection failed with this as well. In both cases I did all the wipes and formats just like the first time. After that I gave up and decided to try to put my Tab back to ICS using the CWM backup I made as recommended before I started the first time. I'm no novice as far as computing is concerned but I haven't rooted an android device before.
If you take a look around the forums here you will find I am not the first to fail to find the nightly files. Perhaps a sticky with the link would be useful?
I install nightlies of CM10 onto my nexus 7 original 16GB every time one is released (which is probably not a good thing but there you go) and i upgraded from the release on 15/12/2012(4.1.2) to the release on (4.2) (I missed a day) but when i had installed i couldn't open Google Play Store which was strange and my favorite live wallpaper 'Microbes' wasn't on the device so i tried to downgrade back to the nightly from 15/12/2012 which was still downloaded on my device. This went smoothly until it came to the first boot where it has been stuck at the CM10 boot animation which is spinning but doesn't stop.
Does anybody know what has happened that could help me? I think it might be something to do with downgrading from 4.2 to 4.1.2. Also i use the CM Downloader that is built into Settings > About
Thanks in advance
DecDuffy
EDIT: I fiddled around with the buttons and managed to get it to restart booting but it is in the never ending boot animation again
EDIT2: I booted into recovery and then installed the nightly from 17/12/2012 and it is working to the same extent that it was before i tried to downgrade
DecDuffy said:
I think it might be something to do with downgrading from 4.2 to 4.1.2. Also i use the CM Downloader that is built into Settings > About
EDIT2: I booted into recovery and then installed the nightly from 17/12/2012 and it is working to the same extent that it was before i tried to downgrade
Click to expand...
Click to collapse
From these and from what i've found when fastboot flashing, i suspect that the either the bootloader changing when upgrading to 4.2.1 from 4.1.2 or the kernel changing caused you the trouble when trying to go back. if you want to check, you could try going into fastboot and see what bootloader version you have, and then try going back to the 4.1.2 build and checking that again. next, compare these with the bootloaders for stock 4.2.1 and 4.1.2. I suspect that in order to move back you would need to do what you did to move back to 4.1.2, then use fastboot to flash the older bootloader to allow it to work. But i'm not certain on that.
and you tried wiping data(factory reset) and reflaahing?
I successfully built Omni from the Android-4.4 branch today for my N8013, but when I go to flash it I get an error:
set_metadata_recursive: some changes failed
and then the flash fails. I was on TWRP 2.6.0.0 so I updated to 2.6.3.0 which appears to have fixed this error on Nexus 7 (see http://forum.xda-developers.com/showpost.php?p=47027929&postcount=114 ), but that didn't help. Anyone have any ideas?
I realize this is completely bleeding edge stuff so I'm perfectly happy to wait a few days, but that said it would be awesome if anyone knows how to fix this. One thing I haven't tried is flashing the recovery image built in tree, but as I just copied the recovery parameters from a repository that's over a year old I'm not sure if they're still valid. And mine is 5.1MB whereas the one from TeamWin is 6.4MB, so probably something is not right there.
My device tree(s) are below:
https://github.com/ibrahima/android_device_samsung_n8013/tree/android-4.4
https://github.com/ibrahima/android_device_samsung_n80xx-common/tree/android-4.4
Using TheMuppets for proprietaries.
edit: Maybe this is promising? http://forum.xda-developers.com/showthread.php?p=47156977
Last time I had a set_metadata_recursive issue, it was actually from changing the order of the vendor/omni/custom.mk include
But there are probably many ways this could happen - especially on the 4.4 branch, you can assume that this is going to be highly unstable and break in all sorts of strange ways for the first few weeks.
I would suggest that if you're doing a device bringup, start with the 4.3 branch and don't mess with 4.4 until you know it's at least working with 4.3
Ah thanks, that's interesting. I did get 4.3 to work, but that was kind of boring . I also realized that the reason my recovery was smaller was that it was the AOSP recovery, rebuilt with TWRP and it was fine. Will try flashing again with the in tree built recovery later today (after resyncing and all that).
Update: Flashed the recovery built in tree, and then was able to flash my build successfully, so that's that. However, now I'm getting a black screen upon booting and nothing else. To me this seems kind of odd because the same blobs worked fine for Omni 4.3, but I don't know what's changed since then or whatnot. Probably should do a resync and rebuild in case anything that's recently gone into android_device_samsung_smdk4412-common helps.
Oh, I see, I think I might need to update to mali r3p2? Will give it a shot...
Hi all,
After a looong night flashing and downloading again and again trying different methods, I'm out of ideas.
I have a uk n9005 (btu) that was happily running out of the box 4.3 stock until yesterday night. No root, no flash attempts before.
I started by flashing german 4.4 (dbt) without wiping before (big mistake, maybe) and without pit file and no repartition nor bootloader update checked. The error came out and I flashed again with the pit file. I let the phone reboot, but it didn't go further than the boot animation. I take out the battery and boot in the recovery. That is when I saw the can't mount \data error for the first time.
I tried to wipe, although it was impossible since the data was not mounted. However I could (and still can) wipe cache. I restarted the phone, and again the same situation, stuck in boot animation. From this moment I've tried many things:
- Flashing the bootloader separately and then the rom. no results (data not mounted and stuck in boot animation)
- Flashing custom recovery and after, official cm11 nightly and another cm11 based rom. no results (data not mounted and stuck in boot animation)
- Downgrading to 4.3. Not possible. Thank you Samsung!
- Firmware recovery with kies 3.0. no results since 4.4 has not been released for my region (maybe waiting for if to come out would be a solution)
- Flashing Polish and german (againg) 4.4 with and without pit file. no results (data not mounted and stuck in boot animation)
The only thing I can think of that I haven't tried yet is flashing a custom kernel, but I can't see any advantage in doing that. Next approach is taking it to the technical service to see if they can solve this situation. I'm afraid they're going to ask for almost as much money as a new note 3 costs...
P.D: I know I haven't taken part a lot in this forum, but I've been reading it for years, since I started playing with my SGS back in 2011. This is the first time I'm really lost after spending the night searching the forum (not only the note 3 section). This really pisses me off, with my previous phones I could always find a way to bring them back to life, but with SGS4 and SGN3 things are totally different thanks to samsung. (sorry for this looong post)
Thank you in advance
wrong place, sorry
move to q&a or delete please
Contruk27 said:
Hi all,
After a looong night flashing and downloading again and again trying different methods, I'm out of ideas.
I have a uk n9005 (btu) that was happily running out of the box 4.3 stock until yesterday night. No root, no flash attempts before.
I started by flashing german 4.4 (dbt) without wiping before (big mistake, maybe) and without pit file and no repartition nor bootloader update checked. The error came out and I flashed again with the pit file. I let the phone reboot, but it didn't go further than the boot animation. I take out the battery and boot in the recovery. That is when I saw the can't mount \data error for the first time.
I tried to wipe, although it was impossible since the data was not mounted. However I could (and still can) wipe cache. I restarted the phone, and again the same situation, stuck in boot animation. From this moment I've tried many things:
- Flashing the bootloader separately and then the rom. no results (data not mounted and stuck in boot animation)
- Flashing custom recovery and after, official cm11 nightly and another cm11 based rom. no results (data not mounted and stuck in boot animation)
- Downgrading to 4.3. Not possible. Thank you Samsung!
- Firmware recovery with kies 3.0. no results since 4.4 has not been released for my region (maybe waiting for if to come out would be a solution)
- Flashing Polish and german (againg) 4.4 with and without pit file. no results (data not mounted and stuck in boot animation)
The only thing I can think of that I haven't tried yet is flashing a custom kernel, but I can't see any advantage in doing that. Next approach is taking it to the technical service to see if they can solve this situation. I'm afraid they're going to ask for almost as much money as a new note 3 costs...
P.D: I know I haven't taken part a lot in this forum, but I've been reading it for years, since I started playing with my SGS back in 2011. This is the first time I'm really lost after spending the night searching the forum (not only the note 3 section). This really pisses me off, with my previous phones I could always find a way to bring them back to life, but with SGS4 and SGN3 things are totally different thanks to samsung. (sorry for this looong post)
Thank you in advance
wrong place, sorry
move to q&a or delete please
Click to expand...
Click to collapse
You might also be able to get it working by flashing the sweetrom like people with the HongKong note 3 had to do to go to KK rom...
Worth a shot if you try everything else and aren't getting anywhere but you will need to be rooted to flash a custom rom...
So, I've been trying to root my Galaxy s5 for a while now and I just got it to work successfully a few hours ago. With that, I installed CWM and everything was fine.
Now, I downloaded the latest nightly of CM12 for the S5 and I threw it on my SD card and ran my phone with the up volume home and power thing, selected the zip and it's now looping. It's been looping for maybe 25-30 minutes. It stopped and said it was upgrading apps for optimization, rebooted and is now stuck on the loading screen for CM12.
I literally know nothing about CM12 or rooting or any of it, I just successfully did it today, so I'm extremely new and know nothing. I didn't factory restore my device, I didn't do anything fancy like that, the tutorial didn't say that I needed to, I just selected it and installed and rebooted.
I tried taking the battery out, and it's still doing the same thing.
Any help is appreciated.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck