I have been modifying the Sony kernel sources, and porting our 4.1 kernel to a 4.2 CAF branch to be used with CyanogenMod 10.1 and above. We will eventually receive Android 4.3 direct from Sony, and therefore suitable kernel sources, but if we can beat them to it, why not?
However our Xperia SP has a very temperamental screen, it really needs a perfect frame buffer or it will crap out on you with no apparent way back.
If you flash a kernel with a broken frame buffer (a kernel that does not send the correct signals to the display), you will see nothing on the screen, sometimes random vertical lines, then your device will get into a low level bootloop, (ADB will not be available) and even if you flash a working kernel from a factory image this will not recover the device. Basically, the screen gets stuck in a non-functional state, the device is able to detect this and immediately hard resets, so your device seems hard bricked.
Well... almost.
Fortunately, Sony build into their factory images a special lock that, on first boot, nothing can cause the device to shut down or reboot. Therefore to break this hard brick, you need to do a full wipe with flashtool.
On reboot the screen will still be broken, but it will do a full boot (you will eventually hear touch sounds when pressing the screen). You can now hit the power button to switch off the display, hit it again and your screen should, finally, come back to life.
* * * * * * * * * *
Why does this happen? My guess is that a specific set of commands must be used to control the display. Any deviation from that set and the screen gets stuck in a non-functional state, and the only way to recover is to eventually send the correct off/on sequence to it.
However this can only happen from a working rom, but due to the auto detect of the broken screen and hard reset (forcing the hardware to switch off without sending an off command to the screen), this can only happen after a full wipe to recreate the first boot sequence.
Therefore if you are experimenting with the kernel you need to be aware of this... 'feature' and that luckily there is a way to recover from it.
I have needed to recover my device three times now with this method and I haven't even owned it for a week yet. I have never seen such behaviour on any of the other devices I have worked on, so this is going to make kernel porting a tricky and tedious affair. The fact that the screen 'remembers' your bad kernel even after you flash a good one is pretty disturbing. (I even left my Xperia SP powered off for over an hour to see if the lack of power would reset the screen, but no change)
Thanks for the more detailed info.
Thanks @adfad666 for the info.
I'm currently looking at framebuffer now and it should be fixed pretty soon then all you guys can have a CM and I'll get eagleeyetom to unlock the thread.
Still continuing
uberlaggydarwin said:
Thanks @adfad666 for the info.
I'm currently looking at framebuffer now and it should be fixed pretty soon then all you guys can have a CM and I'll get eagleeyetom to unlock the thread.
Click to expand...
Click to collapse
adfad666 fixed it in THIS POSTpost.
Kernel is now much more stable, no issues of permanently broken displays across flashes. Also we now have logcat:
logcat: http://pastebin.com/A0VyPDh5
kmsg: http://pastebin.com/TNE1awUy
:victory::victory::victory:
adfad666 said:
Kernel is now much more stable, no issues of permanently broken displays across flashes. Also we now have logcat:
logcat: http://pastebin.com/A0VyPDh5
kmsg: http://pastebin.com/TNE1awUy
:victory::victory::victory:
Click to expand...
Click to collapse
At mean that all of us is ready for cm10.2 development on our device??
best regards.
sanzNya
sent from my mind via tapatalk 4
Oh, great information @adfad666 , thanks alot, hopefully I'll have the deivce in 1 or 2 weeks, and I could help u on the development. (I'm not a kernel developer expert, but for sure I'll learn from you) Thanks in advanced for this, it is really helpful for new SP users. Following your github Thanks.
bieltv.3 said:
Oh, great information @adfad666 , thanks alot, hopefully I'll have the deivce in 1 or 2 weeks, and I could help u on the development. (I'm not a kernel developer expert, but for sure I'll learn from you) Thanks in advanced for this, it is really helpful for new SP users. Following your github Thanks.
Click to expand...
Click to collapse
Biel? Oh dear! I followed your development on the 5830i since day one, back when I had that phone! Hope you'll be bringing CM to this phone too
Sent from my C5303 using xda app-developers app
Updated the thread.
adfad666 said:
Kernel is now much more stable, no issues of permanently broken displays across flashes. Also we now have logcat:
logcat: http://pastebin.com/A0VyPDh5
kmsg: http://pastebin.com/TNE1awUy
:victory::victory::victory:
Click to expand...
Click to collapse
Updating this thread with a link to the CM port from @adfad666 & Kali- and myself.
https://plus.google.com/111440315650679525393/posts/PeAj8dgoNHA
You can look at our kernel source to look at frame buffer.
Related
Ok, to get things working better and faster, let us put together a develoment team... any voluntary???
m0rph3us said:
Ok, to get things working better and faster, let us put together a develoment team... any voluntary???
Click to expand...
Click to collapse
Hmm, don't have any expierence with it, but if I can help just count me in.
I will try to make myself useful. I will also have to learn a lot about android development though...
I'd help, you can count me in, too!
i'm not so great at coding..
maybe i'll learn it while helping you guys.
I can give you guys updates on android versions working on the niki(from other phones)
and then i'll upload it.
im not great at coding, but count me in
Hi!
one android rom for niki??? wooow I'm very interested.
I'm no cook but would be very grateful!
Sorry about the language I use google translator ...
Greetings
m0rph3us,
Hi, I can help with something.
I've ported tinboot NAND bootloader to Nike.
Everything works exclude: sound, screen and board turn off, charging in poweroff state, buttons backlight, camera and bluetooth. phone still cannot enter sleepmode and gets hot as hell in few minutes. but it works from NAND.
I've already asked dzo about problems with Nike and he answered that "more hardware needs to be initialized by kernel".
patch is aviable here, maybe I will upload NBH's if anybody insterested.
and also, may be it is time to start public git repo somewhere? github, gitorious, sourceforge...
rzk333 said:
m0rph3us,
Hi, I can help with something.
I've ported tinboot NAND bootloader to Nike.
Everything works exclude: sound, screen and board turn off, charging in poweroff state, buttons backlight, camera and bluetooth. phone still cannot enter sleepmode and gets hot as hell in few minutes. but it works from NAND.
I've already asked dzo about problems with Nike and he answered that "more hardware needs to be initialized by kernel".
patch is aviable here, maybe I will upload NBH's if anybody insterested.
and also, may be it is time to start public git repo somewhere? github, gitorious, sourceforge...
Click to expand...
Click to collapse
Hi rzk333, just take a look at the threads and I must be honest to all the guy's in this thread but unfortenally this is far above my hat, I really would like to help you guy's but I need my phone for cooking, is there another way to help you all.
Regards
to rzk333
Have you tried this http://forum.xda-developers.com/showpost.php?p=5452606&postcount=184 from tinboot thread. Zenity made this procedure make WiFI and GPS work. I also believe that all hardwares are generated from haret. Maybe you can pick out something from there to initialize some hardware?
Good luck!
Maybe you can pick out something from there to initialize some hardware?
Click to expand...
Click to collapse
we have more complicated case here with Nike than with Kaiser, that method was needed to store wifi calibration and some gps stuff.
With Nike we need to trace everything that happening with kernel when it boots with HaRET (and winmo initialized hw) and when in boots from nothing (hw from NAND coldboot), and find differences\bugs. See dzo's patches on NAND boot for Kaiser/Polaris and patch for preparing Vogue for nand in linuxtogo git repo.
I have the theory and tried everything, but I'm not good at kernel C and reversing from winmo, maybe someone will be interested in NAND boot and help.
ps: sorry for bad English.
rzk333 said:
m0rph3us,
Hi, I can help with something.
I've ported tinboot NAND bootloader to Nike.
Everything works exclude: sound, screen and board turn off, charging in poweroff state, buttons backlight, camera and bluetooth. phone still cannot enter sleepmode and gets hot as hell in few minutes. but it works from NAND.
I've already asked dzo about problems with Nike and he answered that "more hardware needs to be initialized by kernel".
patch is aviable here, maybe I will upload NBH's if anybody insterested.
and also, may be it is time to start public git repo somewhere? github, gitorious, sourceforge...
Click to expand...
Click to collapse
Hey its great, do you have an nbh or the source??? the hardware stuff is initialized by the kernel, and i am working on the sleep, seems that dzo an crew made some changes that prevent the phone to sleep well or to wake up.
Maybe you already know this pdf, but for me it was new and it looks quite useful:
http://www.google.de/url?sa=t&sourc...OpJS_zOMczG0SC8BQ&sig2=kKCUMR0pwEKXNoJl2bVI6Q
The google search stuff is there by intent, as the direkt link to the file on the ftp gives an error (550: Permission Denied )
Thanks, i did not have this pdf.
I have compiled the NBH for booting from nand, it work except the things rzk333 menthioned above... It is a start, i will see what i can do...
m0rph3us said:
Thanks, i did not have this pdf.
I have compiled the NBH for booting from nand, it work except the things rzk333 menthioned above... It is a start, i will see what i can do...
Click to expand...
Click to collapse
can you upload the NBH for us?
can you upload the NBH for us?
Click to expand...
Click to collapse
no problem, here they are, NBH's with dzo's kernel for now.
I cant compile kernel from our git with sleep fixes, throws "arch/arm/kernel/vmlinux.lds.S:6: fatal error: asm-generic/vmlinux.lds.h: No such file or directory", so I set pm.sleep_mode to 0 in kernel cmdline.
http://rzk.sadistto.net/NIKIIMG-320.NBH - 240*320
http://rzk.sadistto.net/NIKIIMG-428.NBH - 320*428
http://rzk.sadistto.net/NIKIIMG-480.NBH - 320*480
remember, this can really wipe your phone out, USE ONLY AT YOUR OWN RISK. I'm not responsible for anything happen with your device.
To compile the kernel from m0rph3us git you nee to merge dzo's kernel in somehow. I can compile it if i copy the code from the git over the files of a copy of dzo's source, thuss loosing some of the newer patches.
I also managed a full merge by hand, but this takes some time and has to be repeated after each git pull.
If you want the phone to wake up with sleepmode 1 set you can also patch in my commit from m0rph3us git in dzo's kernel (its a one line patch). I know that full sleep still won't work, but at least it doesn't hang when the screen powers of. It gives me a good battery life with an older ion build.
rzk333 said:
we have more complicated case here with Nike than with Kaiser, that method was needed to store wifi calibration and some gps stuff.
With Nike we need to trace everything that happening with kernel when it boots with HaRET (and winmo initialized hw) and when in boots from nothing (hw from NAND coldboot), and find differences\bugs. See dzo's patches on NAND boot for Kaiser/Polaris and patch for preparing Vogue for nand in linuxtogo git repo.
Click to expand...
Click to collapse
I have not tried android yet with my HTC devices, but I wonder if booting Android is easier on a security unlocked device where it is possible to load and execute an app bootloader from ram without need for starting WM. I'm referring to my FrankenKaiser SPL loader published here.
rzk333 said:
no problem, here they are, NBH's with dzo's kernel for now.
I cant compile kernel from our git with sleep fixes, throws "arch/arm/kernel/vmlinux.lds.S:6: fatal error: asm-generic/vmlinux.lds.h: No such file or directory", so I set pm.sleep_mode to 0 in kernel cmdline.
http://rzk.sadistto.net/NIKIIMG-320.NBH - 240*320
http://rzk.sadistto.net/NIKIIMG-428.NBH - 320*428
http://rzk.sadistto.net/NIKIIMG-480.NBH - 320*480
remember, this can really wipe your phone out, USE ONLY AT YOUR OWN RISK. I'm not responsible for anything happen with your device.
Click to expand...
Click to collapse
I´m using it and works perfect (until now) except for the sleep.
using this:
http://forum.xda-developers.com/showthread.php?t=619980
folowing this:
http://forum.xda-developers.com/showthread.php?t=636024
Thanks a lot, waiting for the sleep mode fix.
Ok, i noticed that there is no audio at all...
Ok, i noticed that there is no audio at all...
Click to expand...
Click to collapse
thats our main problem, nobody will use that without normally working GSM calls and sound.
dzo changed rpc engine in last commits again, maybe it will fix sound, but it is only a guess.
rzk333 said:
thats our main problem, nobody will use that without normally working GSM calls and sound.
dzo changed rpc engine in last commits again, maybe it will fix sound, but it is only a guess.
Click to expand...
Click to collapse
plz check ur pm bro
regards
Hey guys,
I've discontinued my work on the custom ROM for the galaxy ace, due to the fact that the only person who I knew, who had this phone, actually broke his phone (because it fell or something)..
Also I do not have enough time to work on it properly, so I hope someone else can continue my work (Peeter123?) and open a new topic concerning this...
Intentionally left blank
Looks good, will try to help if I can. Also: Wifi definitely needs fixing. Constant crashes in std samsung build.
Maybe it would be nice to build in ext3 and ext4 support.
I will focus on speeding up the fw first, maybe do some kernel hacks later..
Are you running the new XEKB1 firmware from samfirmware . com already? If so, could you supply me with a copy of your /system folder? Im missing some files/dirs from the fw at the moment..
Thanks!
Sent from my GT-I9000 using Tapatalk
Sure no problem, I will get to that this afternoon
Ps. I'm indeed running the latest firmware (S5830XEKB1)
Will there be a simplified safe step by step tutorial in the near future on how to use this ROM? (and if it ****s up how to restore to factory default or so) I tried messing around with ROM manager with my first model and it bricked so I'm really careful with the new one I got now (yes I tricked the people at the store to get me a new one).
You can restore firmware with odin relatively easily. Even if the main firmware is ****ed up. How bad was it bricked? And was it possible to turn your phone on in download mode?
jeffdijkstra said:
Will there be a simplified safe step by step tutorial in the near future on how to use this ROM? (and if it ****s up how to restore to factory default or so) I tried messing around with ROM manager with my first model and it bricked so I'm really careful with the new one I got now (yes I tricked the people at the store to get me a new one).
Click to expand...
Click to collapse
Yes, before I post the first version of this ROM I will include a guide on how to succesfully flash this ROM and how to fix a broken/bricked Galaxy Ace again... reading through Peters posts (on this and other topics) hopefully he can help me with producing this..
There is no topic for Galaxy Ace! Why? I think there shold be a lot of developer...
Jonathan_m84 said:
I will focus on speeding up the fw first, maybe do some kernel hacks later..
Are you running the new XEKB1 firmware from samfirmware . com already? If so, could you supply me with a copy of your /system folder? Im missing some files/dirs from the fw at the moment..
Thanks!
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
What files do you need. Whole /system folder is a tad big
NVM uploading to my webserver now, I'll send you a PM with the link.
peeter123 said:
You can restore firmware with odin relatively easily. Even if the main firmware is ****ed up. How bad was it bricked? And was it possible to turn your phone on in download mode?
Click to expand...
Click to collapse
It wanted to reboot so I could back-up my current firmware, but it never did, all I ever managed to get was taking it into a 'connecting..' state within Kies when I used one of the three button tricks but nothing appeared on screen.
No matter what combination I tried or what kind of method, the screen stayed black.
Hmm yea that's what I feared. I guess you messed up your bootloader. A broken bootloader is unrecoverable. Everything else is fixable.
See first post!
Sent from my GT-I9000 using Tapatalk
Jonathan_m84 said:
Status(17-03): working on it: deodexed and zipaligned all the apk's, added root and busybox.. however I need to borrow the galaxy ace of a friend of mine to create an ODIN flashable ROM, maybe next week it will be onlibe for you guys!
/***************************************************************************************************************************
WARNING
This release contains a lot of bugs and is purposed for testing only. It's not ready for daily use!
Don't flash this rom if you aren't able to solve some problems without our help.
Don't make any feature requests!
***************************************************************************************************************************/
and:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
Jonathan_m84 .. can u help me? i acidently play with the rom and now i think its bricked.. coz cannot start. and nothing on screen.. when i try push all button then insert battery then connect to pc.. it will detect as samsung mobile modem.. so.. how can i flash with odin?? coz it says setup connection.... stuck there. tq
fahmitue said:
Jonathan_m84 .. can u help me? i acidently play with the rom and now i think its bricked.. coz cannot start. and nothing on screen.. when i try push all button then insert battery then connect to pc.. it will detect as samsung mobile modem.. so.. how can i flash with odin?? coz it says setup connection.... stuck there. tq
Click to expand...
Click to collapse
First of all, I do not own a galaxy ace. Secondly, please dont post this in this topic, use other topics for basic questions, since it does not concern my ROM, especially since my ROM is not published online yet.
When it is, I will provide help for problems with my ROM in this topic, but not with others ROMs, sorry..
Good luck anyway!
Sent from my GT-I9000 using Tapatalk
Okay im not that bad for a person, so let me give you some advice:
*------------------------------------------------------------------------------------------*
Flashing your phone usually means putting leaked software on your phone and thus could potentially
break the rights you have that if it breaks down you get a new one.. so its up to you to proceed..
Before Flashing, make sure you have backed-up all your data, otherwise you'll risk losing it.
Secondly, try to read through some forums/sections (maybe about other phones) to know what
it is you are going to do.
Third, install the right drivers for your phone make sure that KIES is not running on your computer!
Shut it down, shut it down, please do so!.. You just needed to install it to get the Galaxy Ace Drivers,
but the rest of the program is only for people who don't know what to do with their phones,
if you are one of them: Stop reading and be satisfied with what you got, or wait for Kies updates!
*------------------------------------------------------------------------------------------*
Okay, now for the flashing:
Make sure your battery is charged all the way up to 100%, if not you can **** up your battery stats (which are restored after charging it up and playing with it for a couple of days, but nevermind)..
Before connecting it to your computer, shut it down and pull the battery!
Also, make sure that your computer wont be killed/shutdown because your laptop battery is empty or your little brother plays with electricity or something, and try to close as many applications on your computer as possible, just to be sure..
Proceed to the flashing, following these guidelines:
Firmware Update Steps, follow the exact order!:
*-------------------------------------------------------------------------------------------*
1. Run Samsung Galaxy Ace S5830 Downloader
2. Select OPS file : Cooper_v1.0.ops in the OPS field.
3.
- Click BOOT button and select: APBOOT_S5830xxxxx_xxx...._user_low_true.tar.md5
- Click Phone button and select: MODEM_S5830xxxxx_xxx...._REV03.tar.md5
- Click PDA button and select: CODE_S5830xxxxx_xxx...._REV03_user_low_true.tar.md5
- Click CSC button and select: CSC_S5830xxxxxx_xxx......_REV03_user_low_true.tar.md5
4. Put your phone into Download Mode: Press middle Key ( OK key ) + Power + Volume Down
5. Connect USB cable to your phone and the program must read the Com number it takes.
6. Click Start button and the update process will start.
7. Do not touch or remove anything till the device rebooted and you can see PASS word on the program!!
*---------------------------------------------------------------------------------------------*
And that's it, that's all I can do for you at the moment. Maybe next week I'll have some more expierence with flashing the galaxy ace, as of now I have only flashed my Galaxy s (a million times) and my Samsung Star (three times ), so I'm not an expert on flashing a Galaxy Ace.
Ugh, was hoping for the ROM instructions
Anyway, I'm fairly new to Android and ROM's, I rooted my phone already successfully so I could get things like Adblocker for apps etc.
I understand and have been told that ROM's are supposedly the 'better' firmwares out there when they are designed for a phone, thus saving things like battery life and performance, is this true or is this really ROM depended?
I'm mainly looking for things like extending the battery life of my phone (performance speed is way enough already with stock firmware), would this be a good reason to use a custom ROM or shouldn't I bother?
Did you tried everthing in ACE..just reconfirming...
You can increase battery life by disabling data network when you dont use it and by removing all those fancy widgets from your desktop launcher, they eat up battery juice.. also, install advanced task killer froyo from market and kill your running apps that you dont use, set security to low
Sent from my GT-I9000 using Tapatalk
Jonathan_m84 said:
You can increase battery life by disabling data network when you dont use it and by removing all those fancy widgets from your desktop launcher, they eat up battery juice.. also, install advanced task killer froyo from market and kill your running apps that you dont use, set security to low
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Tested a few days with and without ATK. There was no difference. Much better battery life with Juice Defender.
So yeah as the title states my internal screen is completely scattered, I can't use touch anymore nor see anything. But when my device is turned on and I connect it via Usb to my PC I hear the Usb connection sound. My Device is rooted and I think the debug mode is unfortunately deactivated.
Is there any way I can recover my Music and Pictures? Maybe through recovery mode? Or just a programm that bypasses the lockscreen?
I tried a lot hope someone can help me!
Thanks in advance!
-Removed for Personal Information-
Is there no way?
You should be able to use ADB to copy your stuff from your phone to your PC, and you won't need to guess what's on the phone's screen while you're doing it. Lots of tutorials on how to use it on here/elsewhere (search).
MistahBungle said:
You should be able to use ADB to copy your stuff from your phone to your PC, and you won't need to guess what's on the phone's screen while you're doing it. Lots of tutorials on how to use it on here/elsewhere (search).
Click to expand...
Click to collapse
I searched about 2 hours for solutions. The problem is usb debug mode isn't activated on my phone so ADB doesn't recognize my device..
You're pretty much boned then & you're going to have to guess where you are in recovery (if you're someone who flashes roms & messes around with your phone I can't see why you wouldn't have USB debugging on by default).
No easy fixes. Unless you want to wait until you've replaced the screen.
Edit - What buttons you need to press to get to where you need to be in recovery in order to mount the card will depend on what version of recovery you have given many kernel builders modify it. Find someone using the same kernel as you & ask them to help you navigate your way thru.
MistahBungle said:
You're pretty much boned then & you're going to have to guess where you are in recovery (if you're someone who flashes roms & messes around with your phone I can't see why you wouldn't have USB debugging on by default).
No easy fixes. Unless you want to wait until you've replaced the screen.
Edit - What buttons you need to press to get to where you need to be in recovery in order to mount the card will depend on what version of recovery you have given many kernel builders modify it. Find someone using the same kernel as you & ask them to help you navigate your way thru.
Click to expand...
Click to collapse
It was a fresh install of RR and so it wasn't activated at the night I destroyed it. Bad Luck I guess ^^ The problem is I won't replace the screen because I got a Galaxy Nexus for the same amount of money the new screen would cost..
So the buttons are not the same in every RR recovery?
Depending on which version of CWRecovery the kernel has/how (if) the kernel dev has modified it will determine how many button presses & how you have to go up/down through menus.
Post in the RR discussion thread & ask someone to walk you through as I suggested yesterday.
Yeah I understand what you mean about the cost to replace the screen Vs cost of a new phone.
Vicious_Colours said:
It was a fresh install of RR and so it wasn't activated at the night I destroyed it. Bad Luck I guess ^^ The problem is I won't replace the screen because I got a Galaxy Nexus for the same amount of money the new screen would cost..
So the buttons are not the same in every RR recovery?
Click to expand...
Click to collapse
Model: ASUS_Z00AD(ZE551ML)
RAM: 4G
Firmware/APP Version: Latest
Frequency: All the time
Rooted/Unlocked: No
APP Name: None/All/System
Hello, all!
I'm pretty sure I'm gonna have to send it back for an exchange, but I tried to wipe the cache partition on my brand new ASUS ZenFone and got impatient. On top of that I forgot to allow USB debugging. So here's what I did, and the problems I'm facing now:
I installed the latest OTA update that was sent
After three hours of trying to find a fix for the notification glitch, I arose to the solution that it was a permanent bug, however seen many reports of clearing the cache to help
Assuming it was the system cache, I powered the phone down and booted into fastboot, then into recovery using a tutorial found on YouTube
I got into the F:/Cache partition by moving the cursor down and selecting "Wipe Cache Partition"
The process was taking longer than expected, so I powered off the phone in what I feel is a catastrophic failure
Problems:
Bootloader is corrupt with only showing the "dead" android with it flashing slow and constantly
Unable to access recovery mode anymore (see above problem)
Able to access fastboot, but no USB Debugging is turned on
ADB can't access the device (most likely because of the USB Debug. turned off.)
I am NOT rooted and DO NOT have a custom ROM like CyanogenMOD
is there any helping the poor thing or do I have to send it back? Thank you for reading if you got this far.
sincerely,
J
Hello
I did the same thing and fixed it by plugging the phone in fastboot mode and typing the following command : fastboot erase cache
I was then able to go back to recovery and flash a full stock rom with adb sideload
Hope it does the trick for you
dapezzz said:
Hello
I did the same thing and fixed it by plugging the phone in fastboot mode and typing the following command : fastboot erase cache
I was then able to go back to recovery and flash a full stock rom with adb sideload
Hope it does the trick for you
Click to expand...
Click to collapse
Thank you for your reply.. TBH, I have no idea how it works, but it does all of a sudden. The first thing I did, tho, was enable USB Debugging. Goddess this was a long and tedious possess that I hope I don't have to go through again.. This is a great case and point where Apple wins in simplicity. But, yes, to that hater who's reading this: I did know what I was doing, I've rooted many androids before, I just got careless.
wolfboytech said:
This is a great case and point where Apple wins in simplicity.
Click to expand...
Click to collapse
Only when Apple works, had my little brother pulling out his hair trying to get an iphone to downgfrade after the upgrade pretty much pissed all over the actual using of the phone for calls... To make matters worse, it was his work phone and he'd just got through updating everyone's phone at the company...
Simple way to go bald and loose a job....
wolfboytech said:
Thank you for your reply.. TBH, I have no idea how it works, but it does all of a sudden. The first thing I did, tho, was enable USB Debugging. Goddess this was a long and tedious possess that I hope I don't have to go through again.. This is a great case and point where Apple wins in simplicity. But, yes, to that hater who's reading this: I did know what I was doing, I've rooted many androids before, I just got careless.
Click to expand...
Click to collapse
Actually it depends on how much you want to get out of your phone. The more you get the trickier it gets. Most people won't run into those troubles because they just got what manufacturers give to them.
wolfboytech said:
Model: ASUS_Z00AD(ZE551ML)
RAM: 4G
Firmware/APP Version: Latest
Frequency: All the time
Rooted/Unlocked: No
APP Name: None/All/System
Hello, all!
I'm pretty sure I'm gonna have to send it back for an exchange, but I tried to wipe the cache partition on my brand new ASUS ZenFone and got impatient. On top of that I forgot to allow USB debugging. So here's what I did, and the problems I'm facing now:
I installed the latest OTA update that was sent
After three hours of trying to find a fix for the notification glitch, I arose to the solution that it was a permanent bug, however seen many reports of clearing the cache to help
Assuming it was the system cache, I powered the phone down and booted into fastboot, then into recovery using a tutorial found on YouTube
I got into the F:/Cache partition by moving the cursor down and selecting "Wipe Cache Partition"
The process was taking longer than expected, so I powered off the phone in what I feel is a catastrophic failure
Problems:
Bootloader is corrupt with only showing the "dead" android with it flashing slow and constantly
Unable to access recovery mode anymore (see above problem)
Able to access fastboot, but no USB Debugging is turned on
ADB can't access the device (most likely because of the USB Debug. turned off.)
I am NOT rooted and DO NOT have a custom ROM like CyanogenMOD
is there any helping the poor thing or do I have to send it back? Thank you for reading if you got this far.
sincerely,
J
Click to expand...
Click to collapse
there is nothing like stupidity in this bro... this is all about curiosity..these problems makes you more aware of ur device and what andriod development actually is.. getting into these problems and solving it gives a great pleasure and confidence in urself.. which APPLE can never give. m sure every android geek is gone through this problem.. so be happy and proud bro.. happy new year.
c_/\/\_k said:
there is nothing like stupidity in this bro... this is all about curiosity..these problems makes you more aware of ur device and what andriod development actually is.. getting into these problems and solving it gives a great pleasure and confidence in urself.. which APPLE can never give. m sure every android geek is gone through this problem.. so be happy and proud bro.. happy new year.
Click to expand...
Click to collapse
Exactly bro! In learning about androids full potential, its all about trial & errors. By the way, speaking of Apple. IPhones are too simple for advanced users/geeks like us [emoji12]
Sent from my ASUS_Z00AD using Tapatalk
Here is TWRP 3.2.1 build for Project Tango K1 ATAP.
Download
gdrive: twrp-3.2.1-yellowstone.img
mailru: twrp-3.2.1-yellowstone.img
Sources
device tree: https://github.com/HighwayStar/android_device_google_yellowstone
kernel: https://github.com/HighwayStar/android_kernel_google_yellowstone
How to install
enable USB debugging in stock ROM and run command: adb reboot bootloader
Unlock bootloader using command: fastboot oem unlock (it will wipe all your user data!)
With unlocked bootloader boot into stock rom and enable USB debugging again. Reboot to bootloader: adb reboot bootloader
Flash recovery image: fastboot flash recovery twrp-3.2.1-yellowstone.img
To boot into recovery you could run adb reboot recovery after booting to stock ROM or use Vol+ Vol- Power combo to boot in bootloader menu and select Recovery using volume keys and confirm by pressing Power.
XDA:DevDB Information
[RECOVERY][TWRP] Project Tango K1 ATAP TWRP 3.2.1, Tool/Utility for the Nvidia Shield Tablet
Contributors
highwaystar_ru
Source Code: https://github.com/HighwayStar/android_kernel_google_yellowstone
Version Information
Status: Testing
Created 2019-02-19
Last Updated 2019-02-19
Any ROMs available for yellowstone? I can see one in use on the LineageOS Statistics page (search 14.1-20190208-UNOFFICIAL-yellowstone)
But I can't find it on xda.
I didn't get it to boot, but I was in a hurry and hopefully just forgot something simple. If anyone gets it working please post details. Hopefully this is legit:
Edit: link removed. Per the developer: "please don't use them. They're experimental, and won't be booting for some time... you run the chance of bricking. Definitely stay away until I make some form of announcement otherwise."
@highwaystar_ru gave me this ROM that is working splendidly on my yellowstone: https://cloud.mail.ru/public/Hmco/XryszodXm
From @highwaystar_ru:
It uses binary files from stock yellowstone and has some issues:
cameras doesnt work, video playback sometimes has artifacts, all cpu
cores always up (without it video playback lags), accelerometer sensor
inverted.
Me and couple of lineage devs working hard to port shieldtablet kernel
to yellowstone, it will allow to use shield binary files and resolve
most problems, but progress are really slow (but there is some
progress lately).
Click to expand...
Click to collapse
shiznit1618 said:
@highwaystar_ru gave me this ROM that is working splendidly on my yellowstone: https://cloud.mail.ru/public/Hmco/XryszodXm
From @highwaystar_ru:
Click to expand...
Click to collapse
Thanks! This is working very well so far for the limited testing I've done. I'll have to take it into the field and see how that goes .
Tried out that ROM , it's pretty good outside of issues listed bluetooth is non functional.
Mobile data , text, wifi etc working.
Back to life
Thanks to highwaystar_ru I was able to install twrp and then lineage 14.1 with Open GApps pico.
I hope that somebody will be able to bring this to 15.1
Please keep up your effort, Hurray I can use my tango again , at least some of it, would be great that bluetooth and cameras working and good luck with the shield software i'll be looking for it . Thanks alot
thanks
worked for me. . with all the restrictions added.. but still brought a perfectly fine tablet from no usage to home automation dashboard device
Great work thank you,
Also i tested that Rom in the thread and it works well despite the reversed sensor, bluetooth (and i report USB on dock non fuctional with rom)
has there been any progress on the Rom at all? thanks.
Any progress with this rom?
Also @shiznit1618 and @highwaystar_ru where are you guys collaborating? If this is a telegram, discord, or other chat group. I'd love to get in and talk, maybe help a bit. I'm currently on arcore devs slack chat but there isn't much activity in their #yellowstone channel.
https://arcore.slack.com
ShapeShifter499 said:
Any progress with this rom?
Also @shiznit1618 and @highwaystar_ru where are you guys collaborating? If this is a telegram, discord, or other chat group. I'd love to get in and talk, maybe help a bit. I'm currently on arcore devs slack chat but there isn't much activity in their #yellowstone channel.
https://arcore.slack.com
Click to expand...
Click to collapse
There does seem to be some active development on GitHub (within the last week) and I also found (from same developer on GitHub) a newer rom based on 15.1 although I couldn't get it to boot, seems I need to update TWRP, but trying to update TWRP it tells me the recovery partition exceeded size, so I assume I have to update boot as well (which I didn't do). i'd suggest checking on GitHub and contacting that developer.
https://github.com/TegraDevelopment/android_device_google_yellowstone
Bazathoth said:
There does seem to be some active development on GitHub (within the last week) and I also found (from same developer on GitHub) a newer rom based on 15.1 although I couldn't get it to boot, seems I need to update TWRP, but trying to update TWRP it tells me the recovery partition exceeded size, so I assume I have to update boot as well (which I didn't do). i'd suggest checking on GitHub and contacting that developer.
https://github.com/TegraDevelopment/android_device_google_yellowstone
Click to expand...
Click to collapse
Where did you find the 15.1 build?
ShapeShifter499 said:
Where did you find the 15.1 build?
Click to expand...
Click to collapse
http://updater.ods.ninja/yellowstone
This is the same project I had mentioned in post #3. I took the link down because it wasnt ready at the time and I've been waiting for the dev to let us know when its working. See post #3 for a quote from him...
But... there is a build from Feb 12. Please let us know how it goes if you try it. :good:
xaxxelous said:
http://updater.ods.ninja/yellowstone
This is the same project I had mentioned in post #3. I took the link down because it wasnt ready at the time and I've been waiting for the dev to let us know when its working. See post #3 for a quote from him...
But... there is a build from Feb 12. Please let us know how it goes if you try it. :good:
Click to expand...
Click to collapse
I have a new issue, my tablet is rebooting constantly. It will crash to a "red battery icon" and then boot back up to the lockscreen. I'm not sure if the battery in my unit is bad or if the battery calibration is messed up. Do you have any ideas what to do here?
My device was restored to stock btw.
ShapeShifter499 said:
I have a new issue, my tablet is rebooting constantly. It will crash to a "red battery icon" and then boot back up to the lockscreen. I'm not sure if the battery in my unit is bad or if the battery calibration is messed up. Do you have any ideas what to do here?
My device was restored to stock btw.
Click to expand...
Click to collapse
Will it stay on while plugged into the dock? Or usb even?
xaxxelous said:
Will it stay on while plugged into the dock? Or usb even?
Click to expand...
Click to collapse
I never got a hold of a original dock, I didn't check to see if keeping it on charge helped.
ShapeShifter499 said:
I never got a hold of a original dock, I didn't check to see if keeping it on charge helped.
Click to expand...
Click to collapse
Did you flash that build from Feb 12?
How did you return to stock? A TWRP backup or do you have original firmware?
Does it keep bootlooping by itself without any input from you or will it sit stable at the lockscreen? Can you keep it turned off?
Depending on the answers to those questions, the first thing I would do is turn it off and plug it in. Let it sit until fully charged. It takes a long time via USB, and even longer if it is on. Not that this is a solution, just troubleshooting...
xaxxelous said:
Did you flash that build from Feb 12?
How did you return to stock? A TWRP backup or do you have original firmware?
Does it keep bootlooping by itself without any input from you or will it sit stable at the lockscreen? Can you keep it turned off?
Depending on the answers to those questions, the first thing I would do is turn it off and plug it in. Let it sit until fully charged. It takes a long time via USB, and even longer if it is on. Not that this is a solution, just troubleshooting...
Click to expand...
Click to collapse
It reboots without me touching. The main OS has a full battery icon but the reboot flashes the red battery icon before booting. I flashed using NVFlash a copy of the stock OS I got from the arcore stack. Someone gave me their APX package that NVFlash requires.
That file is here: https://drive.google.com/file/d/1dv5ZPsczOAp6l9WOgVlbCTuBnbW71L8p
Conversation starts here: https://arcore.slack.com/archives/C68HHETL7/p1549401595001100
Main quote of interest from that chat:
Greg Willard (r3pwn) 1:20 PM
Around 3 mins left on the upload
1:24
What I did in the interest of still letting a device turn on if someone didn't get the chance to back up their persist/persistbk, was I took mine, and scrubbed the mac addresses and serial number. So the macs are set to 00:11:22:33:44:55:66, and the serial num is 012345678.
1:25
... aaaand here you go https://drive.google.com/file/d/1dv5ZPsczOAp6l9WOgVlbCTuBnbW71L8p
Click to expand...
Click to collapse
ShapeShifter499 said:
It reboots without me touching. The main OS has a full battery icon but the reboot flashes the red battery icon before booting. I flashed using NVFlash a copy of the stock OS I got from the arcore stack. Someone gave me their APX package that NVFlash requires.
That file is here: https://drive.google.com/file/d/1dv5ZPsczOAp6l9WOgVlbCTuBnbW71L8p
Conversation starts here: https://arcore.slack.com/archives/C68HHETL7/p1549401595001100
Main quote of interest from that chat:
Click to expand...
Click to collapse
I can't see that convo without an account. Have you asked for help there?
Until I get home I can't really look at that apx. Maybe install TWRP and the ROM from post #4 or a TWRP backup? Without knowing what that apx flashed its hard to say. The ROM from highwaystar_ru (mostly) works. Might at least get you out of the bootloop.
And just to be clear, you did not flash that 15.1 build, right? What were you running before flashing the apx?
Unless TWRP and that LOS 14.1 ROM or a TWRP backup help we've gone off topic for this thread...