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
Related
Hey guys!
I know this topic really dosn't belong here, but i know that the guys in this forum has much knowlegde so i am trying here!
I have this HTC Hurricane phone, and yes i have asked there but no one seems to be able to help, and then i wanted to flash WM6 on it. For that i needed another SPL, which i got from there and flashed it. The flash it self went fine
But for some reason now, the Hurricane can't do anything at all. I can't turn it on normally i just get a white screen after about 10 seconds after i press the power button. The same happens when i try to get to the bootloader (!), all i get is a white screen after about 10 seconds of nothing. When the device shows me this white screen i also can't get it to connect with my PC! The computer dosn't see it at all, not just active sync, but i do not get that windows xp sound when i plug in a usb device.
So, what can i do? Is this a really good example of a bricked device or what?
I hope you guys will accept that i write here. The Hurricane forum is as good as dead, and i know you guys here for your expertise!
~D
I think JTAG or similar or replacing hardware (DOC Module) might save it, but I don't think there is anyway to flash through USB without the bootloader working...
l3v5y said:
I think JTAG or similar or replacing hardware (DOC Module) might save it, but I don't think there is anyway to flash through USB without the bootloader working...
Click to expand...
Click to collapse
okay that was what i thinking too.. well since i got it very cheap i don't think i will spend any money on such operation.. i guess its quite many money?
Just seen this: http://wiki.xda-developers.com/index.php?pagename=Prophet_Rom_Dump
Note that the prompt only comes up for a few seconds and then it will continue to enter the bootloader.
Click to expand...
Click to collapse
The end of it implies that you can load a ROM from the storage card BEFORE bootloader kicks in.
Not sure if this will work on a Hurricane but it might with some modification and a working device :s
l3v5y said:
Just seen this: http://wiki.xda-developers.com/index.php?pagename=Prophet_Rom_Dump
The end of it implies that you can load a ROM from the storage card BEFORE bootloader kicks in.
Not sure if this will work on a Hurricane but it might with some modification and a working device :s
Click to expand...
Click to collapse
Iam lucky for that couse i actually have another hurricane that works! Thank you i will try this on friday or saturday and write back the status.. I hope you will check back..
Iam glad i can allways count on the people in here!
unbrick it
http://forum.xda-developers.com/showthread.php?t=292667
try the alphazero solution =) !!!!
l3v5y said:
Just seen this: http://wiki.xda-developers.com/index.php?pagename=Prophet_Rom_Dump
The end of it implies that you can load a ROM from the storage card BEFORE bootloader kicks in.
Not sure if this will work on a Hurricane but it might with some modification and a working device :s
Click to expand...
Click to collapse
I have just tried the method. But still i do not get anything, but i white screen. I checked that my ROM dump worked by the other phone. It does ask me if i want to install the rom, but on the bricked one, i do not get anything just that white screen
Guess thats it?
Then I think it is a good example of a bricked phone...
G4 rom dump?
Hi xda-members,
I wanted to know if it's possible to backup and restore a G4 device. On the wiki, it says i need a CID unlocked device.
I think if you hardSPL your device, it should be fine (HardSPL circumvents the CID checking procedure).
l3v5y said:
I think if you hardSPL your device, it should be fine (HardSPL circumvents the CID checking procedure).
Click to expand...
Click to collapse
Ok, on another tread. They said if you got an error while backing up you have a CID locked device. And i already have created a backup. So i think it should be fine.
Ladies and Gentlemen I finaly done did it managed to do a cold boot with Android on Niki.I went and bought a second niki which i nearly messed up its all good now I will be posting images and the rom and how i managed to do it next week on Friday for now i just wanna double check if everything is fine or not coz im still having problems when it comes to making and receiving calls
Niki100
Wm6.1 Salvy
Good
But can you post how you did it. I'm not fully convinced. Did you do it using bootloader or any tools from bootup? If not then maybe you post this to http://forum.xda-developers.com/showthread.php?t=544965 . So that the tread can be managed well.
charnder10 said:
Ladies and Gentlemen I finaly done did it managed to do a cold boot with Android on Niki.I went and bought a second niki which i nearly messed up its all good now I will be posting images and the rom and how i managed to do it next week on Friday for now i just wanna double check if everything is fine or not coz im still having problems when it comes to making and receiving calls
Niki100
Wm6.1 Salvy
Click to expand...
Click to collapse
Video proof?
Actually a new thread would be a good idea, the other one isnt updated on the first post, so its harder to keep track of anything new whithout reading a dozen pages...
The FAQ from blaz.andrejcic is very good, but its not mentioned on the first post, so we can only get there if we noticed it on his sig.
Does the cold boot version inhance the speed or has less bugs?
Sorry to ask, but I'd only consider that rom if the OS would work as good as in a android device. :/
Okay guys I rewrote a new bootloader and as i said I bought a new niki just for that purpose and i cant actually flash back to wm6 again coz of the new bootloader i had to write but im actually jotting down the info on how i did it and its quite along process but guys it not yet 100% full proof thats why i dont wanna upload the rom otherwise it will render your niki useless so guys give me 2 weeks and u will have what u need but i still have one problem and the thing keeps on droping calls each and everytime and i still need to figure out what the problem is.At the moment im in process of reversing the process of the bootloader so u can be able to flash willy nilly so check this thread Saturday morning for Pics and the Info
charnder10 said:
Okay guys I rewrote a new bootloader and as i said I bought a new niki just for that purpose and i cant actually flash back to wm6 again coz of the new bootloader i had to write but im actually jotting down the info on how i did it and its quite along process but guys it not yet 100% full proof thats why i dont wanna upload the rom otherwise it will render your niki useless so guys give me 2 weeks and u will have what u need but i still have one problem and the thing keeps on droping calls each and everytime and i still need to figure out what the problem is.At the moment im in process of reversing the process of the bootloader so u can be able to flash willy nilly so check this thread Saturday morning for Pics and the Info
Click to expand...
Click to collapse
I will wait patiently! If all works, I would love to have it! It just has to be reliable for making / receiving calls, text messages and internet...
Donation will of course be in place...
Boylen said:
I will wait patiently! If all works, I would love to have it! It just has to be reliable for making / receiving calls, text messages and internet...
Donation will of course be in place...
Click to expand...
Click to collapse
Definalty, im very interested in an Android cold boot on the Niki and donating! Obviously like you say you need to iron out a few wrinkles before you go public but could you comment on what currently works/what doesn't (i.e. does the camera work?)
Looking forward to any update!
To be honest I'd be more interested in a dual boot solution...
Specially since there is no fully working android build for our machines.
dual boot
actually, i believe in twolf. i would love to see it dual boot.
and i wont sacrifice my niki just to try this stuff. i would suggest a boot loader that wil boot from internal storage (wm) and micro sd(android). what do you think?
stelph said:
Definalty, im very interested in an Android cold boot on the Niki and donating! Obviously like you say you need to iron out a few wrinkles before you go public but could you comment on what currently works/what doesn't (i.e. does the camera work?)
Looking forward to any update!
Click to expand...
Click to collapse
If all this is real, probably what works is the same as what works now, booting from WinMo. When you boot from WinMo, it does not run within WinMo, HaRET loads Linux fully, just as a cold boot solution would. Only difference in my eyes would be that you will not have to wait for WinMo to boot and then load HaRET, you can boot linux directly.
Unless he's also been working on the linux-kernel and modules ofcourse.
Soooo...unless it brings less bugs or more speed, a link to haret on the \windows\startup folder is still the best option?
:/
Win CE + Haret.exe + Android
The better idea is to cook a rom that strip out uneeded feature and strip it down to the core part or Just Windows CE maybe. Then create a command line version of haret that can recieve parameters to boot. something like "haret.exe -file default.txt" then put it in windows\startup folder or in the registry. In this case you wont have a problem with WinMo OS. I been thinking of this before but i don't have knowledge how to do it.
But the fact that niki still dont have fully working android, we still need have to think twice before dealing with cold booting android in out beloved Niki.
It's been 2 weeks
So, I have been waiting patiently for over 2 weeks
Is this thing real?
Is it working?
anyone came up with a way just to load winCE core and then Android? instead of full WinMo?
just FAKE.
Real or not, If it didnt had a dual boot, not many ppl would like to be stuck with a buggy android-only OS.
but its difficult to have dual boot on nike, there are few avaible memory for both ROMs, so they should be very light versions of both OS. Other option is one running on the phone meory and the other on the SD
I think the correct way is to solve those bugs and have an usable android(I prefer it instead of WM)
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.
Dear All,
Before I start, please forgive the repetition, as I know this issue comes up a lot but I've searched all over and can't find a solution for my circumstance. If there's a post I've missed, please direct me there...:fingers-crossed:
I recently received a Lumia 800 with a Qualcomm bootloader, sim-locked to a UK network. The first thing I did was use NSSPro to remove the simlock, which was successful, but I also wanted to debrand and try a custom ROM..
I read round the issue a fair bit and was going to go down the Linux 'dd' route when I spotted the Windows flashing utilties. Ever keen for an easy life, I went ahead and flashed my handset with FunkyRom, apparently making two fatal errors; not backing up my partitions in Linux and not using Linux to do the flash. Laziness stopped me backing up and I'm aware I deserve what I get for that, but the warnings about flashing in Windows were a little harder to spot and I only found those after the event.
ANYWAY....
Unsurpisingly it turns out, the Windows flash bricked the 'phone. I can get it into Qualcomm bootloader mode in Windows and Linux, I can read the partition map (attached), flash it in NSSPro, 'dd' it in Linux and flash it with the Windows tools, but it won't boot past the Nokia logo. After initial flashing the battery went haywire as well and wouldn't hold it's charge much beyond ten minutes. The battery is fine, I have swapped it out for a new one and it works fine in another 'phone, so I'm not sure what that was about. One other thing to note is I've never been able to hard reset it after flashing, the combination of button presses does nothing, no matter how long I hold them down, all that happens is the 'phone reboots if I release the power button.
I've tried many reflashes, replacing the third partition etc but I think I'm just laying s**t on top of s**t now and would appreciate some guidance. I don't think it's terminally bricked because I can still read/write from/to it in Linux, NSSPro etc, but I'm normally a Nokia N9 man, so this partition structure is unknown, I don't know what I'm looking for.
Any help much appreciated, with the note that I realise I ballsed up not making a backup, so you can skip telling me I'm a fool, I'm getting that enough from the missus..!
Sorry for the looong first post,
Squid
Not sure about fixing it as I have the 710, but Im pretty sure you could RMA to the place you bought it, and they would be too lazy to do full checks on what you did to it, send it back to Nokia and send you a replacement
I've bricked tablets and GPUs and phones and RMA'd, and not once have they ever questioned what I did
One phone I RMA'd I'd flashed a German ROM to and everything was stuck in German, UK company just walked me through factory resetting it on the phone, didn't work obviously, so they gave me a new one
Just an idea if you can't fix it yourself
Other options would be taking it to a local phone repair store who have tools to flash bricked phones, there have been a few here who didn't read the "DO NOT FORMAT" posts, and hit the format button bricking their phones, took it to a repair store who flashed it back to a working state for them
Good luck
Hi and thanks for the reply.
I'll be honest, I'm a Nokia N9 man myself, I was hoping to unlock this one as a spare's spare (it looks and feels familiar), so I'm unlikely to be taking it for repair if I can't get it going myself, but it's interesting to hear you've never been questioned about any DIY work you may have done, I've always thought they'd be hot on that...?
I am holding out for a technical hint or two on something I may have borked during the flash itself, and whether that might be recoverable, after all I can get to the bootloader, just whatever I flash on top (FunkyRom, Rainbow Mod etc) just don't load. Also, why doesn't hard reset work on this 'phone? I have questions but I've run out of brains for answers.
Are there generic full partition dumps available to dd in Linux that would be like a vanilla image? Are there specific partitions that may be the problem? If it gets to the Nokia logo but no further, how far in the booting process has it come?
Squid
Hi John,
Maybe you can try this: http://forum.xda-developers.com/showpost.php?p=47076870&postcount=2
Otherwise I can download an original rom for you, maybe you can flash that with nss, just let me/us know.
Greetz,
Rataplan said:
Hi John,
Maybe you can try this: http://forum.xda-developers.com/showpost.php?p=47076870&postcount=2
Otherwise I can download an original rom for you, maybe you can flash that with nss, just let me/us know.
Greetz,
Click to expand...
Click to collapse
Brilliant, I'll take a look at the NSU first, thanks!
Rataplan,
No joy with the NSU Retail I'm afraid. Do you think you could let me have an original ROM please as mentioned? After that, I guess it goes to the bin..
John
Ok, gonna download and upload this evening, keep you informed.
Greetz,
Rataplan said:
Ok, gonna download and upload this evening, keep you informed.
Greetz,
Click to expand...
Click to collapse
Great, thanks!
john smash said:
Great, thanks!
Click to expand...
Click to collapse
Ok John, you can download the rom here: https://dl.dropboxusercontent.com/u/9417919/rm-801.7z , the rom is based on RM801_059L8M3_1750.0805.8773.12220, I also suggest to read this: http://forum.xda-developers.com/showthread.php?t=1457341 and
this: http://forum.dailymobile.net/index.php?topic=77419.0
Greetz,
Many thanks, I'll try it later. I have actually tried those threads you linked previously but I'll take another look.
Cheers,
John
Hey there Rataplan,
No dice I'm afraid. I can't get the phone connected in anything other than Qualcomm mode, so I can't use NCS to flash. I can use NSSPro to flash a file with .nb extension but not the files you uploaded. NSU Retail asks me to connect in Qualcomm mode then doesn't recognise the phone once I do that.
I just don't understand how if I can get to the Qualcomm bootloader, why flashing RainbowMod or FunkyRom/FunkyRom lite doesn't work, do you have any suggestions? Is there a way to check if any of my partitions are corrupted?
JS
EDIT - Just read this post - http://forum.xda-developers.com/showpost.php?p=29583840&postcount=2 and renamed the boot.img of the ROM you uploaded. Now my 'phone shows a 'Three UK' splash screen, then the nokia logo, but still doesn't load. Is there a way to know what stage of the boot the 'phone is getting to before it hangs?
Ha! Got it!
Using the extract and rename method I flashed the 11412 firmware (oldest one in Navifirm) for product code 059M062 and bingo! It boots and there's no simlock...
Thanks for all your help Rataplan, 'phone revived!
:victory:
Great, I know it had to work, that's why I gave you an copy of an older rom, I'm glad you solved it yourself , take care next time.
Greetz,
Rataplan said:
Great, I know it had to work, that's why I gave you an copy of an older rom, I'm glad you solved it yourself , take care next time.
Greetz,
Click to expand...
Click to collapse
Will do..
I've changed my product code with NSSPro but if I try to flash any later ROMS then it goes back to being borked. I can always recover to this ROM now but I'm wondering why I can't upgrade?
john smash said:
Will do..
I've changed my product code with NSSPro but if I try to flash any later ROMS then it goes back to being borked. I can always recover to this ROM now but I'm wondering why I can't upgrade?
Click to expand...
Click to collapse
I have to take a look at your product code, did you try Nokia Update Retrailer.
The original product code was 059L7C6, I've successfully flashed it with a ROM for product code 059M062 and confusingly, I've written the product code 059L7C2 with NSSPro..
Does it bork it if you try to update it through Zune ?
*Detection* said:
Does it bork it if you try to update it through Zune ?
Click to expand...
Click to collapse
Hey,
Just plugged it into Zune now and it's offering me 7.10.7740.16. Question: Does using Zune overwrite the Qualcomm bootloader? Once that's gone I know I can't get any custom ROMS loaded on here..
Thanks,
JS
For those who may be interested:
I've got a working Lumia now, flashed with a 12220 firmware on a UK product code but that's it, I can't get anything more up to date on there. Every time I flash something more recent I get stuck at the Nokia screen. In addition, I get the same result with any of the custom ROMs, they just won't load. Could my hardware version be preventing the upgrade? Any ideas..?
JS
john smash said:
Hey,
Just plugged it into Zune now and it's offering me 7.10.7740.16. Question: Does using Zune overwrite the Qualcomm bootloader? Once that's gone I know I can't get any custom ROMS loaded on here..
Thanks,
JS
Click to expand...
Click to collapse
No the update doesn't overwrite the bootloader, I flashed the unlocked bootloader to mine and have flashed custom & stock & custom & stock in that order and everything stayed unlocked
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...